&zzz
+FreefallHeavens
+R4SAS
+RN
+ReturningNovice
+StormyCloud
+T3s|4
+acetone
+cims
+dr|z3d
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
zzz
orignal, re: SSU2, I checked my notes, where I call it a "clone attack"
zzz
eyedeekay told me about it in May, for both SSU2 and NTCP2. I told him to tell you NTCP2 was not affected, and you agreed
zzz
on 6/11 eyedeekay sent me more details. On 6/12 I suggested he ask you to write it up as a proposal
zzz
on 6/25 he replied that you agreed to write it up
zzz
afaik that's where we still are today, and that's still my recommendation
zzz
even if you don't want to put in the work yet to document a solution, starting the proposal with a description of the problem/attack is the best way to start
dr|z3d
Is there any value in reverting the mega segmented netdb patch until it's refactored?
dr|z3d
I mean, it's still early enough in the commit tree to pull it, rework it, and then recommit it when it's fixed, ideally in scoped commits and not one huge "throw everything in and cross fingers" commit.
eyedeekay
You mean the merge commit?
eyedeekay
I'm not against reversing it but erasing the history of the master branch doesn't seem good, if I do it I'll have to find a way to do it without that