openresty / openresty/encrypted-session-nginx-module
An IV should be generated for each encryption
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 203
- Forks
- 50
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 2
Description
If you do not generate a per encryption IV your setup is not semantically secure, see http://en.wikipedia.org/wiki/Initialization_vector
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
Start by locating the encryption entry point and the code that constructs the initialization vector. Review how encryption requests obtain IVs and identify the existing tests, if any, that cover repeated encryptions. Done should mean each encryption uses a fresh IV and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100