-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Bad permissions on ~/.ssh/authorized_keys in 1.8.5 #7667
Comments
There is a manual patch available that will fix this issue until the next release: #7610 |
Ah, looks like this is a dupe then. Thanks @shadoxx! |
this still does not work.. any one willing to help ? |
same for me... actually doesn't work yet. |
@SchnWalter, yes I know about this. But in my case I provided vagrant box for developers. And I need fix this automatically. Without manual manipulation |
@ixolt, a quick (insecure) workaround would be to go back to the old ways of using Vagrant VMs with the default insecure key
|
still doesn't work in vagrant 1.8.6. can issue be reopened ? |
@lmeyemezu Hi! If you are still seeing this problem, please open a new issue and include all the information requested. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Vagrant version
1.8.5
Host operating system
Mac OS X 10.11.6
Guest operating system
Ubuntu (12.04 and 14.04)
Vagrantfile
Debug output
Available upon request.
Expected behavior
After provisioning an Ubuntu guest, the file
/home/vagrant/.ssh/authorized_keys
should be readable only by thevagrant
user (600). This is the case in guests provisioned under Vagrant 1.8.4 and earlier.Actual behavior
In Vagrant 1.8.5, the
authorized_keys
file generated during provisioning is both readable and writable by thevagrant
group, and is also readable by others (664). This can create issues if, for example, the file's group ownership is changed, which will causesshd
to refuse the connection and log the errorAuthentication refused: bad ownership or modes for file /home/vagrant/.ssh/authorized_keys
.Steps to reproduce
precise64
ortrusty64
box.vagrant ssh
ls -la ~/.ssh
References
None.
The text was updated successfully, but these errors were encountered: