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.

Sign up for GitHub

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

Jump to bottom

KEM Combiner Option 2a #160

Closed

fluppe2 opened this issue Nov 28, 2024 · 0 comments · Fixed by #161

Collaborator

fluppe2 commented Nov 28, 2024 •

edited

Loading

Prepare a proposal for Option 2a from https://mailarchive.ietf.org/arch/msg/openpgp/NMTCy707LICtxIhP3Xt1U5C8MF0/ with the additions that

we spell out mlkemCT and mlkemPK to explicitely accomodate the flexibility for the use of future KEMs without rewriting the security considerations but still aligning to https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/
we add "OpenPGP" for domain separation

i.e.

KDF ( mlkemSS || tradSS || tradCT || tradPK || mlkemCT || mlkemPK || algid || "OpenPGP" )

At the same time propose to drop the final hashing step (introduced for CCA conversion) in the encap/decap of X25519 and X448 and adopt the corresponding reasoning in https://eprint.iacr.org/2024/039 in the security considerations. This further aligns with https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-kem/.

fluppe2 linked a pull request

that will close this issue

Align KEM Combiner and drop ECDH-KEM CCA-conversion #161

Merged

fluppe2 closed this as completed in #161

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment