[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7582 [Tor]: Don't disable exits so harshly for unexpected END_REASON_EXITPOLICY
#7582: Don't disable exits so harshly for unexpected END_REASON_EXITPOLICY
------------------------+---------------------------------------------------
Reporter: nickm | Owner:
Type: defect | Status: needs_revision
Priority: major | Milestone: Tor: 0.2.3.x-final
Component: Tor | Version:
Keywords: tor-client | Parent: #5456
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by rransom):
Replying to [comment:3 nickm]:
> Roger had a good idea at https://lists.torproject.org/pipermail/tor-
dev/2012-December/004280.html :
>
> >I had this same thought while rereading my earlier message: just
prepend a reject rule for this ip:port to our local version of the relay's
exit policy.
> >
> >It does let the exit "tag" you with an IP:port combo that you'll never
come back to it with. But that seems a small risk compared to the risk of
an exit relay with a complex enough policy that it causes clients to spend
two circuits for fetching each component of web pages.
It's not such a small risk for an IPv6-capable web-browsing client.
How hard would it be to put that âtagâ on the circuit's data structure
instead of the relay's?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7582#comment:4>
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