*HiWe had the same problem yesterday.Using the command "vagrant ssh --
-vvv" you can discover more about the permission issue in the log.The
permission issue with "vagrant ssh" on the windows environment is normally
because the private_key file created during "vagrant up" has more than one
permitted user.Please check the security permissions of the "private_key"
file. It should only have you as a user in the list of permitted
users/groups.Only in that case, shh accepts the private_key file as really
private.If you change the permissions, "vagrant ssh" should work.As this
has to be performed after every "vagrant up", you could consider change the
permission settings of - in your case - the directory "vagrant-boxes".Use
for instance the windows line-command "E:> icacls vagrant-boxes
/inheritance:r /grant <your user name>:(OI)(CI)F"Kind regardsWeit*
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/aa62fdcf-086b-41d8-ac89-432c7fda1430%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
