-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-10.0
-
openssl-3.5.1-1.el10
-
No
-
Low
-
3
-
rhel-security-crypto
-
ssg_security
-
16
-
26
-
0.2
-
QE ack, Dev ack
-
False
-
False
-
-
Yes
-
Crypto25Q1, Crypto25Q2, Crypto25July
-
-
Pass
-
Not Needed
-
Automated
-
Known Issue
-
-
Proposed
-
None
When oqsprovider-0.8.0 is used to generate ML-KEM private keys (to PKCS#8 files), the keys are stored as concatenation of the expanded private key and public key value, not as seed or just the expanded value.
This is in conflict with https://datatracker.ietf.org/doc/html/draft-ietf-lamps-kyber-certificates-06 draft and all the other proposed formats.
- depends on
-
RHEL-72720 liboqs can't derive private key from passed-in seed
-
- Closed
-
- relates to
-
RHEL-82676 Describe key conversion from oqsprovider into a standard format
-
- Release Pending
-
- links to
-
RHBA-2025:148482 openssl bug fix and enhancement update