[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2822 [Tor Client]: fix for 2279 causes addresses mapped to private addresses to fail
#2822: fix for 2279 causes addresses mapped to private addresses to fail
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.2.x-final
Component: Tor Client | Version: Tor: 0.2.2.23-alpha
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by Sebastian):
I think nickm is right, we do seem to check that we don't cache private
addresses in all cases where it matters, except in the case where we ask
to resolve a private address directly (here we'd warn anyway). Isn't it
more likely that you were accessing a resource that actually tried loading
content from a private IP address? Trying to connect to "localhost" seems
to confirm that.
This actually led me to discover two more issues: We don't ratelimit the
log message, so a website that tries to include a lot of local content can
easily spam your log. And if someone asks to resolve localhost, we ask a
lot of exits before accepting that we don't get an answer we'll like.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2822#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