aboutsummaryrefslogtreecommitdiffstats
path: root/p2p/discover/table_test.go
Commit message (Collapse)AuthorAgeFilesLines
* cmd/bootnode, eth, p2p, p2p/discover: use a fancier db designPéter Szilágyi2015-04-241-3/+3
|
* cmd/bootnode, eth, p2p, p2p/discover: clean up the seeder and mesh into eth.Péter Szilágyi2015-04-241-3/+3
|
* p2p/discovery: fix broken tests due to API updatePéter Szilágyi2015-04-241-3/+3
|
* p2p/discover: fix off by one error causing buckets to contain duplicatesFelix Lange2015-04-011-0/+42
|
* p2p/discover: implement node bondingFelix Lange2015-04-011-100/+70
| | | | | | | | | | | | | | | | This a fix for an attack vector where the discovery protocol could be used to amplify traffic in a DDOS attack. A malicious actor would send a findnode request with the IP address and UDP port of the target as the source address. The recipient of the findnode packet would then send a neighbors packet (which is 16x the size of findnode) to the victim. Our solution is to require a 'bond' with the sender of findnode. If no bond exists, the findnode packet is not processed. A bond between nodes α and β is created when α replies to a ping from β. This (initial) version of the bonding implementation might still be vulnerable against replay attacks during the expiration time window. We will add stricter source address validation later.
* p2p/discover: deflake UDP testsFelix Lange2015-02-091-0/+12
|
* p2p/discover: add node URL functions, distinguish TCP/UDP portsFelix Lange2015-02-071-110/+6
| | | | | The discovery RPC protocol does not yet distinguish TCP and UDP ports. But it can't hurt to do so in our internal model.
* p2p/discover: add some helper functionsFelix Lange2015-02-061-3/+3
|
* p2p/discover: new package implementing the Node Discovery ProtocolFelix Lange2015-02-061-0/+403