#2602 closed research (wontfix)

Simple Sybil Attack (ISP level attack)

Reported by: anonymous maybe Owned by: zzz
Priority: major Milestone: undecided
Component: router/netdb Version: 0.9.41
Keywords: sybil Cc:
Parent Tickets: Sensitive: no


We all know in the Sybil attack that the network of lets say I2P already has active peers (not related to the attacker) and the attacker will just create many numbers of nodes in order to luckily catch the traffic. Well what about a simplified version:

ISP blocks all I2P traffic (including iron curtain method, which blocks the outside world and keeps the local connected) , and the ISP allow and spread couple of hundreds nodes (even if its not generated by one machine , even if its not within the border , but all of them controlled by the ISP).

This method will ease the the Sybil and giving it a 99% successful.

How can I2P prevent this situation? What can be done to at least give awareness to the user if its happened (detectable method)?


Child Tickets

Change History (1)

comment:1 Changed 16 months ago by zzz

Resolution: wontfix
Status: newclosed

I don't think there is any way to do what OP is asking.

Note: See TracTickets for help on using tickets.