Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ecdsa-sha2-nistp256 private key support #1375

Open
ctoesca opened this issue Mar 9, 2024 · 1 comment
Open

ecdsa-sha2-nistp256 private key support #1375

ctoesca opened this issue Mar 9, 2024 · 1 comment

Comments

@ctoesca
Copy link

ctoesca commented Mar 9, 2024

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

@cdrage
Copy link

cdrage commented Aug 6, 2024

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

Debugging + troubleshooting, I am also experiencing an error where this also does not work with ecdsa-sha2-nistp521.

praveenkumar added a commit to praveenkumar/crc that referenced this issue Aug 7, 2024
Key generated using ecdsa algorithm is causing issue for podman remote
connection on podman desktop side because the library they consume
doesn't have support for this algorithm. This PR is switching the ecdsa
to ed25519 which is supported by the library consumed in podman desktop.

[0] containers/podman-desktop#8351
[1] mscdex/ssh2#1375
praveenkumar added a commit to praveenkumar/crc that referenced this issue Aug 7, 2024
Key generated using ecdsa algorithm is causing issue for podman remote
connection on podman desktop side because the library they consume
doesn't have support for this algorithm. This PR is switching the ecdsa
to ed25519 which is supported by the library consumed in podman desktop.

[0] containers/podman-desktop#8351
[1] mscdex/ssh2#1375
praveenkumar added a commit to praveenkumar/crc that referenced this issue Aug 8, 2024
Key generated using ecdsa algorithm is causing issue for podman remote
connection on podman desktop side because the library they consume
doesn't have support for this algorithm. This PR is switching the ecdsa
to ed25519 with openssh type which is supported by the library consumed
in podman desktop.

[0] containers/podman-desktop#8351
[1] mscdex/ssh2#1375
praveenkumar added a commit to crc-org/crc that referenced this issue Aug 20, 2024
Key generated using ecdsa algorithm is causing issue for podman remote
connection on podman desktop side because the library they consume
doesn't have support for this algorithm. This PR is switching the ecdsa
to ed25519 with openssh type which is supported by the library consumed
in podman desktop.

[0] containers/podman-desktop#8351
[1] mscdex/ssh2#1375
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants