Consensus on response encryption section
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This issue keeps track of the fact that there is not yet consensus on the response encryption section (section 3 at the time of issue creation). Comments on this section can be done here, but will likely result in opening separate more detailed issues for the actual discussion.
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 by reading section 3, identified as the response encryption section at issue creation, and review the discussion collected here. This issue does not define a concrete change; its stated outcome is consensus, with any implementation or editorial work expected to move into separate, more detailed issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100