Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

thedudeza

thanks

Simon T wrote:

This happens if the path or file name contains spaces. WinSCP adds quotes at the beginning and end of the "Private key file" field which causes the error message. Deleting the quotes fixed the problem for me.



Thank y ou so much!!!
martin

Re: Can't use private key to auth

Thanks for your report and resolution!

This bug has been added to the tracker:
https://winscp.net/tracker/1130
MikeDawg

Simon T wrote:

This happens if the path or file name contains spaces. WinSCP adds quotes at the beginning and end of the "Private key file" field which causes the error message. Deleting the quotes fixed the problem for me.


That was the problem. Thank you sir!
Simon T

This happens if the path or file name contains spaces. WinSCP adds quotes at the beginning and end of the "Private key file" field which causes the error message. Deleting the quotes fixed the problem for me.
MikeDawg

Can't use private key to auth

Using latest WinSCP 5.5.1. I'm unable to use private key for authentication, inside WinSCP.

I got to configure the sftp site I'm attempting to connect to, I go to Advanced Site Settings, go to SSH -> Authentication -> Private key file:

Now, beforehand, I was given a private key file, from openssh. I opened it in Pagent, and converted (exported private key) as a PPK file. When I try and select this PPK, I get the error message:

"File '"C:\<path to ppk>\private_key.ppk"' does not exist or it does not contain private key in known format."

This same PPK file, however, will load into pagent, and I can auth using WinSCP and pagent; but I would just like to cut out the pagent middle-man, and just run the auth from WinSCP.