Closed xmmmmmovo closed 3 years ago
Depending on how you generate your keys. Current OpenSSH behaviour
So, if you use:
ssh-keygen -o
gives this first line:
-----BEGIN OPENSSH PRIVATE KEY-----
Try PEM option:
ssh-keygen -m pem -f /path/to/key
Then you see
-----BEGIN RSA PRIVATE KEY-----
'It is still possible for ssh-keygen to write the previously-used PEM format private keys using the -m flag' from: [https://man.openbsd.org/ssh-keygen#m]
Depending on how you generate your keys. Current OpenSSH behaviour
So, if you use:
ssh-keygen -o
gives this first line:
-----BEGIN OPENSSH PRIVATE KEY-----
Try PEM option:
ssh-keygen -m pem -f /path/to/key
Then you see
-----BEGIN RSA PRIVATE KEY-----
'It is still possible for ssh-keygen to write the previously-used PEM format private keys using the -m flag' from: [https://man.openbsd.org/ssh-keygen#m]
Thanks to reply my problem! After appear this problem, I have been search for solution on Google, and finally I solve this probem by using another plugin named sftp
P.S. This problem caused by the dependency named ssh2-sftp-client
(has been proposed in the repository's issue)
Description
When I use private key to deploy my code to my remote server, it says that "Cannot parse privateKey". But I always use this key to login my remote server.
Example config
Screenshot
Error in vscode:
success to ssh my remote server:
I usually use sftp to deploy my project, so I think it's not my server configuration's error.
Your environment