[tor] Approaching ISPs
Patrick O'Doherty
p at trickod.com
Tue Jan 24 00:30:00 UTC 2017
I hadn't considered that, and it does make a lot of sense to keep this
isolation for the purposes of dealing with 3rd parties and explaining
the relationship between Noise{bridge,tor}.
On the subject of "other things the Tor network could use help with"
I've seen requests for more meek bridges of suitable capacity
(~150Mbps+). *However* there is an open question and active debate as to
how comfortable the community is with Exit operators also running large
Bridge relays due to the potential to deanonymize users.
I think we should push forward with Exit capacity for the moment and
once we have a solution turn our attention to other projects that might
benefit the Tor network/community.
Andy Isaacson:
> It has been useful to be able to clearly say "the Noisetor machine is in
> a different city, at a different ISP, on a different network and IP
> block" than everything else the Noisebridge community uses. The clear
> distinction helps to differentiate Tor-exit-traffic from the rest of
> Noisebridge traffic and services.
>
> So I'm not sure that putting an exit node on Monkeybrains is a great
> idea from that point of view, it means there's a more complicated
> statement to make.
>
> There are other non-exit roles that the Tor network could use help with,
> for example directory authorities (but there are many other roles too,
> I'm not specifying dirauth as the most appropriate one). One of those
> might be a better match for adding to the Monkeybrains network.
>
> -andy
>
> On Mon, Jan 23, 2017 at 02:14:18PM -0800, Cooper Quintin wrote:
>> A long time friend of mine is their longest standing employee, I could
>> make an introduction.
>>
>> On 01/23/2017 12:37 PM, Patrick O'Doherty wrote:
>>> Monkeybrains also provides colo services[0]
>>>
>>> Maybe we should reach out to see if they'd be willing to host an Exit at
>>> their mission facility? It would appear that costs might be reasonable
>>>
>>> [0] - https://www.monkeybrains.net/colocation.php
>>>
>>> Ben Kochie:
>>>> What we really would like is to buy bandwidth in a new colo facility
>>>> we're
>>>> moving to. If Monkey Brains has cross-connects into Equinix, we'd
>>>> love to
>>>> talk.
>>>>
>>>> On Mon, Jan 23, 2017 at 8:01 PM, Cooper Quintin <cooperq at eff.org>
>>>> wrote:
>>>>
>>>>> Let me reccomend Monkey Brains as an ISP that might be willing to host
>>>>> an exit node as well.
>>>>>
>>>>> On 01/23/2017 11:00 AM, mark burdett wrote:
>>>>>> There are some tor exit nodes running on Hurricane Electric,
>>>>>> operated by
>>>>>> three different people (one of whom works at Naval Research Lab),
>>>>>> according to https://torstatus.blutmagie.de/
>>>>>>
>>>>>> I guess this makes Hurricane less ideal than another ISP with no
>>>>>> nodes.
>>>>>>
>>>>>> No details at
>>>>>> https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs
>>>>>> https://trac.torproject.org/projects/tor/wiki/doc/ISPCorrespondence
>>>>>> except mention of "cheap he.net <http://he.net> bandwidth" in a note
>>>>>> about another ISP
>>>>>>
>>>>>> --mark B.
>>>>>>
>>>>>> On Mon, Jan 23, 2017 at 9:58 AM, Patrick O'Doherty <p at trickod.com
>>>>>> <mailto:p at trickod.com>> wrote:
>>>>>>
>>>>>> A very quick search across the archive shows few results for HE
>>>>>> specifically.
>>>>>>
>>>>>> The most promising is from 2013 with someone claiming that "My
>>>>>> colo
>>>>>> provider Hurricane Electric understands Tor"
>>>>>> https://lists.torproject.org/pipermail/tor-relays/2013-
>>>>> March/001956.html
>>>>>> <https://lists.torproject.org/pipermail/tor-relays/2013-
>>>>> March/001956.html>
>>>>>> which doesn't seem to be the case in our situation.
>>>>>>
>>>>>> Patrick O'Doherty:
>>>>>> > This might be an interesting thread to cc the tor-relays list
>>>>>> about. I'd
>>>>>> > search for HE in the archives first though.
>>>>>> >
>>>>>> > The HE policies in question for others to view
>>>>>> > * TOS https://he.net/tos.html
>>>>>> > * AUP https://he.net/aup.html
>>>>>> >
>>>>>> > Things like AUP section 2.2 "No customer shall do anything that
>>>>> could
>>>>>> > get any portion of Hurricane Electric's IP space ... put on
>>>>>> blacklists"
>>>>>> > are things we can't possibly comply with given the nature of
>>>>>> the
>>>>> Exit.
>>>>>> >
>>>>>> > Ben Kochie:
>>>>>> >> Patrick and I approached HE about running an exit via their
>>>>>> network. We
>>>>>> >> were up front and honest.
>>>>>> >>
>>>>>> >> They came back with a non-answer reply of "Have you read our
>>>>> terms of
>>>>>> >> service?"
>>>>>> >>
>>>>>> >> Of course we can't promise anything, and given the overly
>>>>>> broad
>>>>>> terms, HE
>>>>>> >> is not an option.
>>>>>> >>
>>>>>> >> How have we approached vendors in the past?
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> _______________________________________________
>>>>>> >> tor mailing list
>>>>>> >> tor at lists.noisebridge.net <mailto:tor at lists.noisebridge.net>
>>>>>> >> https://www.noisebridge.net/mailman/listinfo/tor
>>>>>> <https://www.noisebridge.net/mailman/listinfo/tor>
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> tor mailing list
>>>>>> tor at lists.noisebridge.net <mailto:tor at lists.noisebridge.net>
>>>>>> https://www.noisebridge.net/mailman/listinfo/tor
>>>>>> <https://www.noisebridge.net/mailman/listinfo/tor>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> tor mailing list
>>>>>> tor at lists.noisebridge.net
>>>>>> https://www.noisebridge.net/mailman/listinfo/tor
>>>>>>
>>>>> _______________________________________________
>>>>> tor mailing list
>>>>> tor at lists.noisebridge.net
>>>>> https://www.noisebridge.net/mailman/listinfo/tor
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> tor mailing list
>>>> tor at lists.noisebridge.net
>>>> https://www.noisebridge.net/mailman/listinfo/tor
>>>>
>>>
>>
>
>
>
>
>> _______________________________________________
>> tor mailing list
>> tor at lists.noisebridge.net
>> https://www.noisebridge.net/mailman/listinfo/tor
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://lists.noisebridge.net/pipermail/tor/attachments/20170124/175bd396/attachment-0003.sig>
More information about the tor
mailing list