Tracking: Questions for Network Audit

[teor2345]

Motivation

This tracking issue contains tickets with questions we want to ask during the network audit.

It is blocked by tasks we want to complete before the network audit.

Issues

• Consider disconnecting from peers with skewed clocks #2167
• Add fixed node IP addresses to initial seed peer config #2274
• Fuzz or property test deserialization with random bytes #2282
  • Coverage-based fuzzing for transaction processing, (de)serialization #2298
  • Coverage-based fuzzing for network message processing, (de)serialization #2299
  • Coverage-based fuzzing for block processing, (de)serialization #2300
  • Implement roundtrip encoding property test for Messages from random bytes #2448
• Use the CandidateSet and AddressBook to connect to initial seed peers #2325
• Zebra should try harder to discover and distribute good peer addresses #1892
• Zebra attempts new peer connections in a fixed, predictable order #1875
• Security: rate-limit outbound messages, Credit: Equilibrium #2153
• Limit fanouts to the number of active peers, Credit: Equilibrium #2214
• Make old Zebra versions eventually refuse to run #1870
• Some DNS seeders and block explorers don't show Zebra nodes #1904
• Zebra should store a persistent list of recent successful peers #1956
• Should Zebra have a time limit on each peer connection, or randomly churn peers?
• Should Zebra track peer reputations, and disconnect or rate-limit bad peers?
• Stop using private IP addresses by default #3117

To Be Confirmed

We want to re-evaluate these tickets before the network audit, to see if we want to fix them, ask questions, or close them.

• Use the CandidateSet and AddressBook to connect to initial seed peers #2325

[mpguerra]

Converted to issue

[teor2345]

It seems like we've answered most of these questions between the Zebra audit and Ziggurat testing.