> On 10 Jan 2018, at 10:23, debug <tracdebug@xxxxxxxxxx> wrote: > > Is there any specific reason why there is no comment from Tor-team for this issue? > > https://trac.torproject.org/projects/tor/ticket/24351 Many of us have been on holidays. Also, the discussion on the ticket is hard to follow. It's long, and it doesn't appear to be progressing. Tickets aren't designed for that kind of discussion. There also appear to be several similar tickets on the same topic. This makes it harder for people to keep up. Maybe there is a response on one of the other similar tickets? Here's what I suggest you do: Blocking an entire CDN would be a major change to either Tor or Tor Browser's design. It's not likely to happen, because of the security vs usability tradeoff. Significantly reducing the usability of Tor would decrease the number of users, making Tor's anonymity set smaller, and reducing anonymity for everyone. Please do some background reading on this part of Tor's design before responding to this email, or adding anything to the bug tracker. Then, if you think this change belongs in Tor, Tor has a proposals process: https://gitweb.torproject.org/torspec.git/tree/proposals/001-process.txt Please submit a proposal with reasons for the change, and a design. If you think this change belongs in Tor Browser, please send a short change proposal to the tbb-dev list. T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev