Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

11/WAKU2-RELAY: libp2p FloodSub & GossipSub: Security Analysis #245

Closed
staheri14 opened this issue Nov 7, 2020 · 3 comments
Closed

11/WAKU2-RELAY: libp2p FloodSub & GossipSub: Security Analysis #245

staheri14 opened this issue Nov 7, 2020 · 3 comments

Comments

@staheri14
Copy link
Contributor

Problem

To analyze the security of the libp2p FloodSub & GossipSub protocols based on #244.
In this analysis, and for each security feature resulted from #244 the following items should be investigated

  1. Attackers and their incentives
  2. Any security measures implemented by FloodSub & GossipSub protocols to address the attacks
  3. To list all the unaddressed threats
  4. To provide DOs and DONTs on how to use FloodSub and GossipSub in order to achieve a higher level of security. This can include any recommendation about activating/avoiding a certain feature/functionality of FloodSub & GossipSub protocols.

This issue is part of #183

Acceptance Criteria

The result shall be a document describing the security guarantees featured by the FloodSub and GossibSub protocols, any instructions on how to activate/utilize those security features. Also, the document should explain the security properties that are out of the scope of these protocols or subject to attack.

@staheri14 staheri14 self-assigned this Nov 7, 2020
@oskarth oskarth changed the title libp2p FloodSub & GossipSub: Security Analysis 11/WAKU2-RELAY: libp2p FloodSub & GossipSub: Security Analysis Mar 31, 2021
@staheri14
Copy link
Contributor Author

Not a priority right now. I am going to unassign myself for now but will get back to it when it becomes a priority.

@staheri14 staheri14 removed their assignment Apr 2, 2021
@oskarth
Copy link
Contributor

oskarth commented Jul 14, 2021

@staheri14 could consider doing this as part of refactor&upstream week, taking existing analysis and opening issue/PR to libp2p specs/forum

@jimstir
Copy link
Contributor

jimstir commented Jun 13, 2024

Closing, issue moved here.

@jimstir jimstir closed this as completed Jun 13, 2024
@jimstir jimstir closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants