docs: clarify X3DH primitive interfaces and passive-secrecy game#3
Open
jinxinglim wants to merge 4 commits intomainfrom
Open
docs: clarify X3DH primitive interfaces and passive-secrecy game#3jinxinglim wants to merge 4 commits intomainfrom
jinxinglim wants to merge 4 commits intomainfrom
Conversation
Document current scope (deterministic, no keygen) and what extensions are needed for security proofs (probabilistic encaps, keygen). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Document current scope (deterministic, no nonce) and what extensions are needed for security proofs (nonce parameter, probabilistic encrypt). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Document the lowercase/uppercase private/public key convention and replace ASCII SK_B with SKᵦ for consistency with SKₐ. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Expand the game description to list the 5 specific private keys (ikₐ, ekₐ, ikᵦ, spkᵦ, opkᵦ) and note that the random key is sampled from SK (the KDF's output space) - Explain why T is embedded at DH3 specifically: it's the only DH value whose computation needs both secret scalars hidden in the DDH challenge (ekₐ, spkᵦ); the other DH values each involve at least one scalar the reduction samples itself Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
ChristianoBraga
left a comment
There was a problem hiding this comment.
@jinxinglim could you please answer my comment?
| embeds T as DH3, queries the ROM on the resulting DH tuple to | ||
| get a session key, and passes it directly to the adversary. | ||
|
|
||
| Why DH3? Among the four X3DH DH values, DH3 = ekₐ • SPKᵦ is the |
Contributor
There was a problem hiding this comment.
Could you revise and elaborate this further?
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.
Summary
Documentation-only refinements made while reading through the X3DH-related files. Adds future-work notes to the primitive interfaces (KEM, AEAD), documents a notation convention in X3DH.lean, and expands explanations in the passive-secrecy game file.
No code/theorem changes — only comments, doc headers, and one cosmetic subscript fix.
Files changed
PQXDHLean/KEM.leanencaps/decaps, nokeygen(sufficient for correctness proofs)encapsand akeygenoperation, plus a suggested refactor pattern (separateKEMSpecalongsideKEM, mirroring theKDF/KDFOraclesplit)PQXDHLean/AEAD.leanencryptfor IND-CPASecurityDefs.leanPQXDHLean/X3DH/X3DH.leanF), uppercase names denote public keys (group elements inG), subscriptsₐ/ᵦindicate owner (Alice / Bob)SK_B→SKᵦ(matches existingSKₐ)PQXDHLean/X3DH/X3DHPassiveMessageSecrecy.leanSK(the KDF's output space)Tis embedded at DH3 specifically: DH3 =ekₐ • SPKᵦis the only DH value whose computation needs both secret scalars hidden in the DDH challenge; DH1/DH2/DH4 each involve at least one scalar the reduction samples itself