Use the "vagrant ssh-config" within your project directory to see where the 
private key is located for your specific project.
If you don't replace the insecure private key, then that standard key 
located at ~/.vagrant.d/insecure_private_key is used.
If you do replace the insecure private key then "vagrant ssh-config" will 
tell you where the private key is located.

And to test your private key,

ssh -p 2222 -i ~/whereever/private/key/is/located [email protected]

And you should be able to login.

This should work the same way "vagrant ssh" works.

Hope that helps.

-- 
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/eeaeb843-614b-4c1b-ba1c-03af8f2d8557%40googlegroups.com.

Reply via email to