[tor-relays] [OrNetRadar] AS: "DigitalOcean, LLC" - 2018-01-16

Robin rok at sent.com
Fri Jan 19 19:42:00 UTC 2018

I've also added those relays to the ExcludeNode with the following options:

ExcludeNodes FD94F9A1FB940786691A7B8A266DCA50C6AE28F1,314E00247E8A661F3FB583275AD3F7B5466EFC99,0DDD78A986EDECA1E6FD36F8C4ACEFBCB95A90D7,3137D94063BA0F5D92BAD71EC4F452CA875D81D3,AF1D8F02C0949E9755C0DF9C6761FBBF7AA$
StrictNodes 1

kind regards, 

my relay EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445

----- Original message -----
From: Iain Learmonth <irl at torproject.org>
To: tor-relays at lists.torproject.org
Subject: Re: [tor-relays] [OrNetRadar] AS: "DigitalOcean, LLC" - 2018-01-16
Date: Fri, 19 Jan 2018 12:52:42 +0000


On 18/01/18 13:16, x9p wrote:
> not doing DROPS anymore, trying not to hurt clients. StrictNodes, via torrc

Note also that if you are a relay, this (and the other node
selection options below) only affects your own circuits that Tor
builds for you. Clients can still build circuits through you to any
node. Controllers can tell Tor to build circuits through any node.

If this did work to restrict clients building circuits through your
relay, this would still have a negative effect on the anonymity
properties of the Tor network as it increases the network fragmentation.
All relays in the consensus should be able to reach all other relays in
the consensus.


tor-relays mailing list
tor-relays at lists.torproject.org
Email had 1 attachment:
+ signature.asc
  1k (application/pgp-signature)

More information about the tor-relays mailing list