secret key encryption page should document guarntees
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 267
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
I believe these are privacy (IND-CPA, -CCA, and NM-CPA) and integrity (INT-PTXT and INT-CTXT), but this should be verified and included in the docs.
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
No file or test is named in the issue. Start by locating the secret-key encryption documentation and reviewing the underlying PyNaCl/libsodium behavior; verify the listed privacy and integrity guarantees before documenting the confirmed properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cryptography, python
- Domain
- cryptography, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100