@eyedeekay
&eche|on
&zzz
+Irc2PGuest3601
+R4SAS
+RN
+StormyCloud
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BubbRubb
Chrono
Dann
DeltaOreo
Irc2PGuest12868
Irc2PGuest27269
Irc2PGuest65801
Irc2PGuest74254
Irc2PGuest79605
Irc2PGuest90985
Irc2PGuest92550
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
Stormycloud_
T3s|4__
Teeed
aargh2
ac9f_
anontor2
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gelleger1
leopold_
makoto
matean
n1
nilbog
not_bob_afk
null911
poriori
profetikla
r00tobo_BNC
solidx66
thetia
uop23ip
w8rabbit
x74a6
orignal
zzz, I have a question about database lookup
orignal
we have noticed in our code that every time we send lookup reply to specified tunnel we use one or our exploratory tunnels
orignal
was there a partcular reason for this or it's just a bug and we should drop reply to IBGW directly?
zzz
orignal, you're a ff, you get a lookup, you're asking if you send it back direct or via a expl. tunnel?
orignal
yes
orignal
any partcular reason why we send through explratory tunnel?
orignal
it seems that only reason was to reudce number of transports at a FF
zzz
that sounds right
orignal
can we reply to IBGW directly?
orignal
number of trsnaports is not loger an issue
zzz
you could do something like (if connected to the target || below connection limits) send direct; else send thru expl. tunnel;
orignal
since we got rid of ElGamal
orignal
thanks
orignal
I will change the code
orignal
it produces severe slowness of lookups
zzz
sure, we send direct, you're not anonymous, the guy that sent the lookup knows what router you are
zzz
sure, especially if you're already connected to the IBGW it's really bad to send it out a tunnel
orignal
zzz, DatabaseStore reply is always non encrypted
orignal
we should do something with it
orignal
as I understand there is only one case of non-encrytped DeliuveryStatus
zzz
you mean the DeliveryStatusMessage that you bundle in a garlic clove with the DatabaseStoreMessage?
zzz
^^ orignal
orignal
no
orignal
I send DatabaseStore and request reply
orignal
non zero reply token
orignal
then a FF sends a DeliveryStatus back
zzz
ok, looking at i2np spec, I see it
orignal
so, if IBGW sees DeliveryStatus
orignal
it means reply of a publication
zzz
I was thinking of the garlics going down client tunnels
zzz
ok, so what's the threat/attack?
orignal
IBGW can collect more information then if it was encrypted
orignal
for example if I'm IBGW I see my role now
zzz
sure but it's not much info
zzz
an IBGW knows it's an IBGW
orignal
most likely I'm part of a leaseset
orignal
no I don't mean this
orignal
if I receive a DeliveryStatus
orignal
I know that another end is part of LeaseSet
orignal
maybe encrypted
zzz
could be an expl tunnel
orignal
I mean published leaseset
orignal
how?
orignal
expl tunnel doesn't have a leaseset
orignal
and RI is published directly
zzz
we'll store RIs out expl tunnels and get a DSM back
zzz
we don't always
orignal
we also don't do it
orignal
only when we can't do it directly
orignal
that's even worse
zzz
the published vs. non-published is interestnig
orignal
published and encrypted leasesets