Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vagrant private key permissions #33

Closed
johnbender opened this issue Mar 19, 2010 · 1 comment
Closed

vagrant private key permissions #33

johnbender opened this issue Mar 19, 2010 · 1 comment
Labels

Comments

@johnbender
Copy link
Collaborator

SSH fails when the default key in the gem isn't set to read write and execute by the owner.

@mitchellh
Copy link
Contributor

Clarifications on this bug I found while debugging it: This error only occurs when the user running vagrant ssh is the same owner as the private key file, and the private key file is not chmodded to 0600.

Therefore, this probably only affects a small number of Vagrant users at the moment, luckily. (Specifically those who installed via RVM or something similar)

That being said, it should be fixed in this changeset: http://github.com/mitchellh/vagrant/commit/b80a08ce8ef5c835c883f9956cb679e583fd4248

I'm going to continue doing some basic testing for a bit, then I'll push this fix out as part of a 0.2.1 most likely.

Mitchell

@ghost ghost locked and limited conversation to collaborators Apr 17, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants