ML-KEM digest fetching
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
I came across that fetching parameters are ignored when creating ML-KEM public key from data. I want to fetch supplementary digests with particular properties.
EVP_KEYMGMT object for ML-KEM supports OSSL_PKEY_PARAM_PROPERTIES only for key generation, not for fetching.
EVP_PKEY_fromdata calls evp_keymgmt_util_fromdata implemented as
Fetching of supplementary digests (SHAKE, SHA3) happens when we call evp_keymgmt_newdata (ossl_ml_kem_key_new callback) and parameters are processed only in evp_keymgmt_import.
Can we improve this situation?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with crypto/evp/keymgmt_lib.c at the referenced evp_keymgmt_util_fromdata code, then trace ossl_ml_kem_key_new and evp_keymgmt_import in the ML-KEM key-management implementation. Reproduce EVP_PKEY_fromdata with OSSL_PKEY_PARAM_PROPERTIES and inspect how supplementary SHAKE and SHA3 digests are fetched. Done means the requested properties are honored when creating an ML-KEM public key and the behavior is covered by validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100