connect(...) promise never rejected with wrong private key
See original GitHub issueWhen I try to connect to a server with a wrong private key, if it’s wrong (change a letter in the key), the promise is never resolved nor rejected.
await (new SftpClient()).connect({
host: configuration.host,
port: configuration.port,
username: configuration.username,
privateKey: configuration.openSshCertificate,
});
When the private key is correct, every thing is ok.
ssh2@1.11.0 ssh2-sftp-client@9.0.3
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Unhandled promise rejection - key path incomplete
I am using a google action to open on google home, ask for an activation keyphrase if the device has not been registered...
Read more >JavaScript Promise Tutorial – How to Resolve or Reject ...
You can create a promise using the promise constructor like this: let promise = new Promise(function(resolve, reject) { // Make an ...
Read more >Incorrect error from invalid private key for signTransaction #1998
Hey guys, I was running into an issue where I was getting an insufficient funds error when trying to sign a transaction.
Read more >Error handling with promises - The Modern JavaScript Tutorial
In the task an error is thrown form inside the promise and promise is never settled neither with a resolve nor reject. The...
Read more >Is rejecting a Promise only for error cases?
Good question! There is no hard answer. It depends on what you consider to be exceptional at that specific point of the flow....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Version 9.0.4 pushed to npmjs.com
Have pushed a fix which should address this issue. Now, when the private key cannot be processed, you should get an error stating the private key could not be parsed with some details indicating why not.
Plase test and let me know if it fixes your problem. I will push a new 9.0.4 version next week.