matrix-org / matrix-org/pinecone
Abuse resistance
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 486
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
(I wrote about this long ago in a matrix room, but someone reminded me to record it here.)
Would be nice to specifically record the possible attack scenarios and how pinecone handles, planned to handle, should handle or fail to handle them. Possibly it is an useful detail whether something depends on the protocol itself, or on an implementation detail which SHOULD be considered and specified.
Suggestions:
- single point flood (DoS)
- distributed flood (DDoS)
- abusive connections to the network
- deliberate/repeated splitting, joining
- nodes dropping, corrupting traffic (especially bootstrap)
(Some or all could be invalid or already described; some of them indeed are described in the wiki but isn't centrally collected. And possibly many more should be added.)
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 reviewing the existing wiki material and the attack scenarios listed in the issue. Determine which cases are already covered and what depends on the protocol versus implementation details; done means a central, agreed document records handling or expected behavior for the relevant scenarios.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, networking, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100