Repository navigation
Add OpenSSL-backed ML-KEM key exchange - #1005
Open
bdewater-thatch wants to merge 3 commits into
Open
bdewater-thatch wants to merge 3 commits into
bdewater-thatch wants to merge 3 commits into
Conversation
bdewater-thatch
force-pushed
the
pq-mlkem
branch
from
June 19, 2026 19:44
6686128 to
29d910a
Compare
Collaborator
|
Thanks @bdewater-thatch! Status update: ruby/openssl#1062 was merged on 2026-06-22 but isn't in a released openssl gem yet (the latest is 4.0.2, from May). This PR now also conflicts with master: the kex lists changed in 8.0 (#925, and #1042 dropped |
bdewater-thatch
force-pushed
the
pq-mlkem
branch
from
October 15, 2026 18:24
29d910a to
e50b7f8
Compare
bdewater-thatch
force-pushed
the
pq-mlkem
branch
from
October 15, 2026 18:31
e50b7f8 to
c3456c6
Compare
Collaborator
|
Thanks for this! net-ssh now uses changelog fragments instead of edits to CHANGES.txt (see the Changelog section of CONTRIBUTING.md), and CI requires one per PR, so I pushed a commit adding |
Collaborator
|
Merged current master into the branch to pick up the latest changes. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for
mlkem768x25519-sha256key exchange. It is dependant on ruby/openssl#1062 getting merged, but locally unit and integration tests pass when running that branch with a crypto backend that supports ML-KEM-768 (eg OpenSSL version 3.5+). When available, net-ssh advertises it ahead of existing key exchange algorithms; when unavailable, behavior is unchanged.OpenSSH 10.0 made
mlkem768x25519-sha256the default key agreement algorithm for post-quantum safety. OpenSSH describes it as NIST-standardized, quantum-safe, no weaker than curve25519-sha256, and faster than the previous default: This is also where public-sector cryptography guidance is heading. NIST finalized ML-KEM in FIPS 203 in August 2024, and government roadmaps are starting to put late-2020s/2030s dates on PQC migration planning.