Add a document on injection and other attack vectors
Open
Nobody has claimed this yet.
enhancement
more
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
RethinkDB is pretty secure from injection, but people still worry about it and other potential attack vectors. We should write a document explaining this.
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
The issue names no file, test, or entry point. First define the document's scope around injection and other potential attack vectors, then identify the appropriate documentation location and supporting security information. Done means a published document explains RethinkDB's injection safety and other attack vectors.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100