Roadmap for post-quantum ssh client
#2037
Replies: 1 comment 1 reply
-
|
We usually rely on libssh for this. They have a great track record of implementing cryptography and rarely lag behind. In cases where we deemed necessary we have done our own implementations (ie, we use OpenSSH for key handling as there were compatibility issues with libssh). So my question is, why should we do this "independent" of libssh? |
Beta Was this translation helpful? Give feedback.
-
|
The PR on this at libssh is currently stuck due to lack of time for debugging: https://gitlab.com/libssh/libssh-mirror/-/merge_requests/400. Would there be any chance for using OpenSSH for their post-quantum work? |
Beta Was this translation helpful? Give feedback.
-
Checklist
Configuration
Not relevant to the issue
Describe the bug
OpenSSH has used
sntrup761x25519-sha512@openssh.comby default since 9.0 (2022) to prevent capture-now decrypt-later attacks.Are there plans for implementing this in Blink’s
sshclient independent of libssh?Beta Was this translation helpful? Give feedback.
All reactions