Age | Commit message (Collapse) | Author |
|
surprises. in the future, i have some ideas for a better way.
|
|
https://leap.se/code/issues/3725)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vagrant key)
|
|
|
|
provider.production.json)
|
|
|
|
|
|
|
|
options -- this should prevent ssh from trying all the keys in ~/.ssh. you might still get the error "Too many authentication failures" if you have a ton of keys activated in ~/.ssh/config
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vagrant reports it's version differently >= v1.3
before: Vagrant version 1.2.2
now: Vagrant 1.3.4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
being updated.
|
|
|
|
/srv/leap/[puppet|bin], because doing so messes up the permissions of /srv/leap.
|
|
|
|
see http://docs.vagrantup.com/v2/vagrantfile/version.html for
details on vagrant command line option and config differences.
|
|
kinds of confusion. originally, i added this to prevent modification of ~/.ssh/known_hosts, but now we do this by just setting UserKnownHosts to /dev/null.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|