Closed prometheas closed 9 years ago
Gah, just realized that you need the private key text itself; not merely a path to a key file. I've submitted a PR for ssh2 which could address this use case.
Closing this issue on this project.
I'm having the same problem, but I'm setting the complete path and the error persistis
Hi, I got the same error message for the new SSH key format. Like to problem explain in this comment: https://github.com/mscdex/ssh2-streams/issues/100#issue-309317656
I needed to convert my key into old format to fix the problem. New format start : "-----BEGIN OPENSSH PRIVATE KEY-----" Old format start: "-----BEGIN RSA PRIVATE KEY-----"
only solution that worked for me was to change to sftp extension instead. No need for converting the file nor generating new one. https://marketplace.visualstudio.com/items?itemName=Natizyskunk.sftp
Hey there. I'm having a devil of a time getting
gulp-ssh
to use my ssh keys; hoping to either get the problem fixed or (perhaps more likely) be educated as to whether I'm maybe doing something bone-headed… but here's the deal.I've got these RSA ssh keys (generated using
ssh-keygen
with a passphrase), and I keep them in~/.ssh
, like any civilized human being might. (Perms on those files are right, just to preempt that particular question — I've been using these keys for the better part of a year to breeze around into various hosts.)The trouble is that whenever I point
gulp-ssh
to my private key and attempt to access a remote host that I routinely access successfully via cli ssh, I get the following error:I don't usually cut my code out, but here's my file: