@eyedeekay
&zzz
+R4SAS
+RN
+T3s|4
+dr|z3d
+hagen
+hk
+mareki2p
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest12735
Irc2PGuest28644
Irc2PGuest4450
Irc2PGuest59134
Irc2PGuest87589
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
acetone_
aeiou
ardu
b3t4f4c3__
carried6590
cumlord
death
dr4wd3_
eyedeekay_bnc
not_bob_afk
onon_
plap
poriori_
profetik1
qend-irc2p
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
orignal
zzz, if your dest supports few encryption types say 4,5 how do you diferentite them when receive rachets new session msg?
zzz
orignal, try both, but PQ is much bigger, so you can be smart about it by checking the size, see 'Ratchet' section under 'Implementation Notes'
zzz
but it's not right because NS has a garlic payload too
zzz
if we're serious about forward secrecy we need to stop sending streaming payload in NS, but that will cost us one RTT
orignal
what if it's 5,6 ?
zzz
you could still do it by size.
zzz
but I don't know if we want to support multiple PQ flavors on same dest. TODO
orignal
but advarsary also can do it by size
zzz
adversary doesn't know if it's NS or NSR or ES
orignal
btw, can we have like 0,4,5,6 ?
zzz
in the proposal I say ElG + PQ is probably unsupported
orignal
agree
orignal
but see, we client most like you will need 4,5,6,7
orignal
for http prpxy
zzz
I think in the beginning we would pick the "best" PQ out of 5-7 (probably 5) and then only support "best,4"
orignal
because eepsite can have any of them
zzz
and leave other combinations for much later
zzz
right, but maybe we leave that for 2028?
orignal
then another question
orignal
what should be set for proxy once PQ is available and there are still eppistes with 0
orignal
you would need like 0,4,5
zzz
true
orignal
how do you think to habdle it?
orignal
we might come to decision to stop supporing Elg completely
orignal
it's just mess in my code
zzz
well, say in 2026 when we're ready, we look to see how many elg-only sites are out there, and make a decision
orignal
i2pd set 4 by defult for server tunnels
zzz
do we tell everybody to upgrade, and change HTTP proxy to 5,4; or do we decide we still need to support ElG, and we change HTTP proxy to 5,4,0 and have to implement that
zzz
I don't know
zzz
I'd rather not support 7,6,5,4,0 )))
zzz
it's just more mess and very inefficient
orignal
my point is that we must come with plan to stop supporting Elg
orignal
4,5 should be fine
zzz
yeah. I think notbob.i2p has some stats on enc types
zzz
if we have a plan, then we can tell people what the plan is and what to do ))
orignal
that's what I mean
orignal
we must come with plan and publish it
zzz
notbob reports: ElG 15 ECIES 274 Both 543
zzz
so that _sounds_ like almost nobody is ElG-only. BUT:
zzz
the problem is SAM apps that aren't setting 4,0, or only changed to 4,0 last year (bitcoin, libtorrent)
orignal
we can set 4 by default in SAM
orignal
or 4,0
zzz
sure, but that's only for the case where people are updating i2pd but not bitcoin
zzz
the concern is we create multiple bitcoin "islands" where there's the 5,4 island and the 0 island, and they can't talk to each other
orignal
either thye update coint or i2pd
orignal
easy
zzz
I'll have to talk to bitcoin about it, the way they pick their seeds
zzz
another problem: there's no way for the router to tell the client (I2CP or SAM) what enc types it supports
zzz
if we stop supporting 0 and client sends a 4,0 LS we will blow up
orignal
we must decline such LS
zzz
yeah, I2CP can check the router version, if we add PQ and/or drop ElG in the same version, and strip unsupported enc types
zzz
if we don't coordinate on the same version then we need some other mechanism
eyedeekay
Android release is tagged and uploaded to Google Play. I haven't been able to fix the tunnel view in portrait mode. As a workaround, the app is defaulting to landscape mode for now. In 2.8.1 I will restore portrait mode.