~dr|z3d
@RN
@RN_
@orignal
@postman
%RTP
+Xeha
+bak83_
+onon_
+qend-irc2p
+r00tobo_BNC
+uop23ip
AHON1
Arch
BubbRubb1
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest10206
Irc2PGuest43010
Irc2PGuest63604
Irc2PGuest89963
Meow
Onn4l7h
Onn4|7h
SigSegv
StormyCloud
T3s|4
T3s|4_
acetone_
anontor2
ardu
boonst_
cumlord
duck
eyedeekay
hk
mareki2p_
maylay
not_bob_afk
pisslord
poriori_
profetikla
r3med1tz
shiver_
simprelay
solidx66
thetia
u5657_
usr003
weko_
zer0bitz_
zzz
eyedeekay
That was hard
eyedeekay
i2p.i2p.2.2.1-nested-netdb has partial isolation now
eyedeekay
All stores are isolated, and all publishes are isolated, but lookups cascade from clients->router netDb still for now which breaks isolation
eyedeekay
But I'm on the last leg of it
eyedeekay
Then I *think* we knock out basically this whole class of netDb attack
eyedeekay
Which is pretty exciting
eyedeekay
There's some fine-tuning to do, it costs memory to have a dozen netDbs, but the client ones are smaller and right now the ones I'm using are bigger than they need to be
obscuratus
eyedeekay: Good to see a light at the end of the tunnel on this one.
eyedeekay
Tell me about it. The extant netDb defenses are impressive in some ways, they're very flexible, but they're extremely difficult to understand and follow on
eyedeekay
I actually will still need to fix one thing about the old defenses after I'm done with this
obscuratus
You said it major. :)
RN
heh
eyedeekay
blinded leaseSets confirmed broken on nested-netDb, I'll fix them and encrypted at the same time before merging it
RN
exciting!