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

Constraints on Public & Private Keys #82

Merged
merged 2 commits into from
Dec 17, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-lamps-kyber-certificates.md
Original file line number Diff line number Diff line change
Expand Up @@ -217,19 +217,19 @@ certificate extension MUST only contain keyEncipherment
--- PRIVATE-KEY no ASN.1 wrapping --
}

ML-KEM-PublicKey ::= OCTET STRING
ML-KEM-PublicKey ::= OCTET STRING (SIZE (800 | 1184 | 1568))

ML-KEM-PrivateKey ::= OCTET STRING
ML-KEM-PrivateKey ::= OCTET STRING (SIZE (32))
seanturner marked this conversation as resolved.
Show resolved Hide resolved
seanturner marked this conversation as resolved.
Show resolved Hide resolved
~~~

No additional encoding of the ML-KEM public key value is applied in
the SubjectPublicKeyInfo field of an X.509 certificate {{RFC5280}}.
However, whenever the ML-KEM public key value appears outside of a
However, whenever it appears outside of a
certificate, it MAY be encoded as an OCTET STRING.

No additional encoding of the ML-KEM private key value is applied in
the PrivateKeyInfo field of an Asymmetric Key Package {{RFC5958}}.
However, whenever the ML-KEM private key value appears outside of a
However, whenever it appears outside of a
Asymmetric Key Package, it MAY be encoded as an OCTET STRING.

# Subject Public Key Fields
Expand Down
Loading