noise: hybrid post-quantum handshake (X25519 + ML-KEM-768)#727
Open
royzah wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Concrete draft for #723, so we have something byte-level to react to instead of an open question.
Additive, separately negotiated handshake that mixes ML-KEM-768 into the
XXpattern via Noise HFS. Advertised ahead of/noise, falls back with no flag day. Auth stays classical (identity key signs the static key), only secrecy is hybridized.Pins the protocol id and suite, defers token/KDF order to Noise HFS. Still open (called out in the doc):
Reference impl: libp2p/rust-libp2p#6481 (off-by-default
mlkem-hfs). Would love go/js eyes early. cc @jxs @thomaseizinger @mxinden @MarcoPolo @achingbrain