RN
is this as interesting as it sounds? Dropping build request with the same previous and next hop
dr|z3d
RN: not really. it's an i2pd thing.
dr|z3d
in + we give them a little 15m ban or thereabouts.
RN
ah. I was thinking some kind of attack trying to get the peer before and after a connection
dr|z3d
shouldn't be permitted, but i2pd allows it.
RN
s/connection/dest
RN
why in the world would they allow that? it just sounds wrong to me.
dr|z3d
ask orignal, he knows :)
RN
оригинально, я был бы признателен, если бы вы могли объяснить логику разрешения этого (или даже разрешения узла в одном и том же туннеле более одного раза)
RN
orignal, I'd appreciate if you could explain the logic behind allowing that (or even allowing a peer in same tunnel more than once)
RN
(oh, it translated the nick too... not seen that happen before.)
orignal
yes, it's possible with i2pd
orignal
tunnel like A-B-A
orignal
we never have A-A-B for example
orignal
but such configuration if possible
orignal
why we allow it?
orignal
because we think it's better for anonymity
orignal
it eliminates possibility for an advesary to assume that peer can appear in a tunnel only once
dr|z3d
yeah, but if that peer happens to be the adversary, not so great.
orignal
that's still a topic to discuss
orignal
even if he is an advasry he doesn't know if it's the same tunnel or another
dr|z3d
maybe not directly, but you can't assume that's the only method an attacker will use to identify where he is in the tunnel chain.
orignal
that's what I mean. Both solutions have pros and cons
RN
thanks for the reply orignal. I'm not sure which is the right solution.