Skip to content
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.

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

Composite private key encoding #119

Open
ounsworth opened this issue Mar 7, 2025 · 0 comments
Open

Composite private key encoding #119

ounsworth opened this issue Mar 7, 2025 · 0 comments

Comments

@ounsworth
Copy link
Contributor

ounsworth commented Mar 7, 2025

From the mailing list:

https://mailarchive.ietf.org/arch/msg/spasm/04czobwhAH7Z0iLx00Ow4Y9MaHY/

have a sequence of octet string representing
the private key octet strings as they would appear in the single key
PrivateKeyInfo object.

This is what we intended to do in the IETF 122 drafts, but we missed updating the private key text. The format would be:

CompositePrivateKey ::= OCTET STRING
where that OCTET STRING is
len(pqkey) || pqkey || tradkey
and the pqkey, trad key are as they would appear in a single-key PrivateKeyInfo.privateKey or OneAsymmetricKey.privateKey.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant