Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abuse resistance #63

Open
grinapo opened this issue Aug 25, 2022 · 0 comments
Open

Abuse resistance #63

grinapo opened this issue Aug 25, 2022 · 0 comments

Comments

@grinapo
Copy link

grinapo commented Aug 25, 2022

(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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant