ecdsa-sha2-nistp256 private key support
Open
Nobody has claimed this yet.
feature request
- Dominant language
- JavaScript
- Stars
- 5.8k
- Forks
- 734
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
When I use 'ecdsa-sha2-nistp256' private key (ppk format), with passphrase:
PuTTY-User-Key-File-2: ecdsa-sha2-nistp256
Encryption: aes256-cbc
Comment: ctop@xmoeexplme1
Public-Lines: 3
AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBInz3Pl1DVKF
7aPjxqwVmlpz4AodXMM0OWIYVtZ9xCFhUSDV+uhUQ8xFgnyG/ZTXk9iAwyQZ37U2
pKKhsPyLiNA=
Private-Lines: 1
eR+n+wx+TD2qG9LMQNlaGKIzUz+yWvtyEQG5iCxZEI4KfM81fy7tyIIBdcchSM2D
Private-MAC: 00d4195a1fe6f4f3145da5417e9bf45eb6d02829
On client.connect(), I have this error:
Cannot parse privateKey: Unsupported key format
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at client.connect() and reproduce the Unsupported key format error with the supplied encrypted ecdsa-sha2-nistp256 PPK key. Trace the privateKey parsing path and verify that the example key is accepted when the passphrase is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100