please describe in detail the exact steps you performed

I was attempting to load the private key for a virtualbox vm created by vagrant. Vagrant names the private key "private_key".

1. First I clicked the "Import..." link
2. I navigated to the private key file vagrant created "D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\private_key".
3. Click open.
4. Click "[Enter] Connect" button to connect.
5. Authentication fails

Since that failed i did the following to fix it.
1. Copied "D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\private_key" to "D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\id_rsa".
2. Click "Import..." link.
3. select "D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\id_rsa".
4. click open.
5. click "[Enter] connect" with successful authentication.

Let me know if there is anymore info you need. I'd be happy to contribute if you can point me in the right direction.

did you try adding an -i flag to use the private_key name ?  or try naming it id_rsa.private_key and see if it loads automatically ?

the behavior you describe sounds like standard openssh behavior.

I tried adding the following to the SSH Arguments without any luck

-i private_key
-i D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\private_key
-i D:/andrew/ubuntu/.vagrant/machines/default/virtualbox/private_key
-i "D:\andrew\ubuntu\.vagrant\machines\default\virtualbox\private_key"
-i "D:/andrew/ubuntu/.vagrant/machines/default/virtualbox/private_key"
-i "/D/andrew/ubuntu/.vagrant/machines/default/virtualbox/private_key"

host paths (outside of Chrome) like D:\xxx make no sense to NaCl processes (like openssh) because the security sandbox provides no visibility at all to the host filesystem.  inside the sandbox, the .ssh dir lives inside /.  so try a path like:
  -i /.ssh/private_key

That worked! feel free to close this. Thanks for clearing that up for me.

could you try installing the file named something like "id_rsa.private_key" and see if it'll work w/out the -i option ?

i'm wondering if we can (or should) make the default behavior a bit smarter.  at the very least, we could add info to the "load key" UI so people are aware of the openssh behavior.

yes, it seems to work as long as i prefix with "id_rsa." so changing the key to "id_rsa.private_key" and "id_rsa.foo" both worked.

 Issue 750000  has been merged into this issue.

 Issue 844271  has been merged into this issue.