IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2026/01/14
&zzz
+R4SAS
+RN_
+T3s|4
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Danny
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
cims
dr4wd3_
dr|z3d
duanin2
hababam
hagen_
leopold
makoto
marek
marek22k
n2
noidea
not_bob_afk2
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
zelgomer
zzz great orignal. I tried an outbound connection to you and hit a bug on my side, fixing now
zzz anyway, yay us! first successful PQ transport test!
dr|z3d nice, nice.
orignal mine is down now
orignal let me know I will start it
orignal also will configure 2RRY
orignal how about other implemnatations?
zzz you wanted to test before we updated and reviewed the proposal, so that would probably be the next step to get go/rust involved
orignal 2RRY should support NTCP2-PQ now
zzz ok thanks. No luck fetching the 2RRY RI right now, will wait a while and try again
zzz CA 2RRYOutbound✓48 sec / 8 sec0 / 08 sec0011
zzz success version 4
orignal right now it has ipv4 issue that's why it runs as ipv6 only
zzz I'll work on updating the proposal and then we can schedule a review for sometime in February
orignal what's outstanding for NTCP2?
zzz just the proposal and review. If go or rust wanted to do different port (v=4) I'd have to code and test that, otherwise I'm not going to bother
orignal I doubt that they are ready
zzz certainly not, and there's no particular rush. But they may have an opinion
orignal also need to discuss paddings
zzz for PQ padding I'm using the same buffer as the message, so max padding == message size (880/1264/1648 for msg 1, 848/1136/1616 for msg 2)
zzz does that sound like enough?
orignal so for 3 you max message size is 880?
orignal or 1760?
zzz no. 880 fixed message size, + 0-880 padding
zzz so 1760
orignal I don't like it
orignal more messages will have size between 1264 and 1760
orignal hence an advesray can recognize 1264
zzz but is anybody going to use 3 enough to worry about it?
orignal idk just saying
orignal manybe for 2 it should be up to 1264
orignal my point is that it should not be peaks around real sizes
zzz I'll think about it and add a section to the proposal
zzz with some TODO markings ))
zzz yup
orignal also I'm thinking to pick 2 or PQ randomly if PQ is available
orignal e.g. if I'm 4 and Bob is 4 I might decided to pick 2
zzz padding and msg sizes is always frustrating to talk about because there's no right answer, only guesses about adversaries and traffic analysis
RN shoulder pads.... so 1980's
RN ;)
orignal maybe always have msgs up to 1648
orignal for all types