[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3535 [Tor Client]: Relax IsolateDestAddr rules to handle hostname/ip distinction
#3535: Relax IsolateDestAddr rules to handle hostname/ip distinction
-------------------------+--------------------------------------------------
Reporter: nickm | Owner: nickm
Type: enhancement | Status: accepted
Priority: normal | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: | Parent: #1865
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by arma):
Replying to [ticket:3535 nickm]:
> The current prop171 branch takes a simplistic view of isolating streams
by destination address, and treats any two addresses as equal only if they
equal in a case-insensitive string comparison. But if address A has
resolved to IP B, then perhaps we don't want to isolate future requests
for A and B onto separate circuits.
If the user actually asks for destinations A and B and they are different,
we should respect the isolation requests. I think it's only where the user
asks for destination A and then asks for destination A again later, and in
between the Tor client has cached the resolve and does a remap for the
second request, that we should realize they're the same.
I could imagine recognizing that they're the same by crawling the
mapaddresses, or by just remembering the "originally requested address"
somewhere in the stream and consulting that when considering isolation.
> There may also be other circumstances like this, such as where hostname
A and hostname B are both known to resolve to IP C.
Open research question whether that's a good idea. So I think it should
default to "no, keep those separate" until somebody gives us a better
intuition.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3535#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs