@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+snex
+wodencafe
Arch2
BubbRubb
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest53192
Irc2PGuest59134
Irc2PGuest59461
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
acetone_
ardu
b3t4f4c3__
bak83
boonst
cumlord
death
dr4wd3_
duck
eyedeekay_bnc
not_bob_afk
phobos
pisslord
poriori
profetikla
qend-irc2p_
radakayot_
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
x74a6
eyedeekay
I've got the basic design of all the first three handshake phases in what I'm calling "MessageProcessors" an NTCP session uses these as handlers for the handshake phases. I've factored out KDF and AEAD operations into interfaces I can centralize on/use and re-use as well. I've got some disorganization between the noise and ntcp interfaces as a by-product of development which is leading to some slightly
eyedeekay
confusing bugs, but my next step is to go back and refactor the noise library to fit with what I know about the needs now, which is going to be about half subtractive, half moving stuff around to better facilitate the structure of the NTCP2 library. Once I've done that I'll have a very clear idea as to what the rest of the implementation bugs are.
eyedeekay
All of which is very straightforward Go development stuff. Basically, I'm cleaning up, and when I'm done cleaning up, it's going to be pretty much ready.