[tor-relays] Netflix overblocking non-exit Tor relays

Jonas Bergler jonas at bergler.name
Sat Feb 27 12:38:48 UTC 2016


Yesterday I forwarded this thread to Neil Hunt - the Chief Product Officer
at Netflix with the hope that he would read it and have received the
following reply a few hours ago.

Noted - this will go to the right technical people.
>

I'm hoping this is a sign Netflix will take this seriously.

-- Jonas

On Sat, Feb 27, 2016 at 12:20 PM, <tor_manager at autistici.org> wrote:

> Hi everyone,
> apparently this is happening with a lot of relays node (My italian relay
> node was blocked too)
> https://www.reddit.com/r/netflix/comments/472kqu/netflix_started_blocking_tor_relayonly_nodes/
> As Roger said we have to try to identify someone inside Netflix to pitch
> "our cause", on the other hand, it will probably be really useful to try to
> step up also in public (social/PR), for example asking to EFF to support
> this.
>
> We are struggling convincing people to open nodes, we really have to
> protect them, we will see a decrease number of nodes
>
> Aidoru
>
>
> On 2016-02-26 23:58, Roger Dingledine wrote:
>
>> On Sat, Feb 27, 2016 at 12:42:38AM +0100, Gero Kuehn wrote:
>>
>>>  They did however not
>>> leave the impression that they a) care or b) intend to fix this at some
>>> point by parsing the Tor network information properly instead of using
>>> whatever cheap&wrong hack they use now.
>>>
>>
>> There is actually a service that they can use to do this parsing
>> for them:
>> https://check.torproject.org/cgi-bin/TorBulkExitList.py
>> e.g.
>>
>> https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=128.31.0.34&port=443
>>
>> Now, I bet Netflix has more than one IP address. It would not be hard
>> to adapt this service to help them do what they should be wanting to do.
>>
>> See https://www.torproject.org/docs/faq-abuse#Bans for more details.
>>
>> One of our next steps might be to find a useful technical contact
>> inside Netflix, so they can start doing this advocacy and education from
>> the inside.
>>
>> --Roger
>>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160227/ff66ab7e/attachment.html>


More information about the tor-relays mailing list