HPKE support for AAD
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.8k
- Forks
- 1.8k
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 157
Description
Currently the HPKE Suite API has encrypt and decrypt argument "info" to provide KDF extra info, but does not have argument "aad" to provide AEAD input of AAD.
Without this, I am not able to validate examples from RFC 9180 which do use AAD.
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 the HPKE Suite API's encrypt and decrypt entry points and compare their current info handling with the RFC 9180 examples. Confirm how AAD should be passed to the AEAD operation, then use those examples as acceptance criteria: callers can supply AAD and the examples validate successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100