~dr|z3d_
@RN
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%snex
+FreefallHeavens
+NiceBoat
+Onn4l7h
+Onn4|7h
+Over
+leopold
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
Arch
Dann
Holmes
Irc2PGuest12976
Irc2PGuest1526
Irc2PGuest28234
Irc2PGuest32287
Irc2PGuest51098
Irc2PGuest78427
Irc2PGuest90624
Meow
OfficialCIA
RTP_
SilentWave
Wikk__
ahiru
cims
dagal
fa
floatyfloatilla7
i2potus
mahlay
makoto
n2_
nilbog
not_bob_afk2
pory
r00tobo[2]
strykpojke
thetia
user1
vivid_reader56
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!