Decide whether to zeroize buffer or encrypt it back on tag check failure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 961
- Forks
- 200
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 6
Description
With one-pass decryption we start to decrypt ciphertext before its integrity was verified. In the case if tag check has failed in the end we need to erase decrypted data. It can be done either by zeroizing the input buffer (as done in ascon-aead, see #659) or by encrypting it back (as done in aes-gcm, see #551).
We probably should look into what is done in other libraries outside of the Rust ecosystem.
Contributor guide
No contributing guide indexed for this repository
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
Compare the zeroization approach used by ascon-aead in issue #659 with the encrypt-back approach used by aes-gcm in issue #551. Survey how libraries outside the Rust ecosystem handle one-pass decryption after tag-check failure; done requires a decided strategy and agreement on the resulting buffer behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100