[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2148 [Torbutton]: 1.3.x: RefSpoofer fails on 5 test cases out of 12.
#2148: 1.3.x: RefSpoofer fails on 5 test cases out of 12.
-------------------------------------------------------------------+--------
Reporter: T(A)ILS developers | Owner: mikeperry
Type: defect | Status: assigned
Priority: blocker | Milestone: Torbutton: 1.3
Component: Torbutton | Version: Torbutton: 1.3
Keywords: TorbuttonIteration20110305 MikePerryIteration20110305 | Parent:
Points: 6 | Actualpoints:
-------------------------------------------------------------------+--------
Comment(by mikeperry):
bee - in general, outgoing link clicks aren't something we're interested
in blocking right now. It is an arms race that really needs to be planned
out if we're even going to attempt it. We would need a way of describing
how outgoing link tracking works on sites and providing a rule language
that allows people to write rules to undo this tracking, like we have done
with HTTPS Everywhere, and like has been done with AdBlock Plus. There are
too many sites doing this to expect to make a dent otherwise. Sure,
Google. Yahoo, and Mozilla are the big ones, but the reality is many other
sites have their own implementations, too.
In this bug, we are only discussing the actual Referer header. You're
right, this is only one side of the problem. But it is one that we *might*
be able to solve, or at least improve, with a single, general change to
browser behaviour.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2148#comment:18>
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