I propose to reject these new DigitalOcean relays (no contact/MyFamily)
+---------------------+------------------------------------------+-------------+---------+----------+----------+---------+ | first_seen | fingerprint | tor_version | or_port | dir_port | nickname | contact | +---------------------+------------------------------------------+-------------+---------+----------+----------+---------+ | 2018-01-16 01:00:00 | FD94F9A1FB940786691A7B8A266DCA50C6AE28F1 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 02:00:00 | 314E00247E8A661F3FB583275AD3F7B5466EFC99 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | 0DDD78A986EDECA1E6FD36F8C4ACEFBCB95A90D7 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | 3137D94063BA0F5D92BAD71EC4F452CA875D81D3 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | AF1D8F02C0949E9755C0DF9C6761FBBF7AAB62C2 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | 5C0C3F106C81BDA139DB1B5CD11E3E8E00C2ECF5 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | B901626F9F7CD538B8B7812223F6614B1CFBDD78 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | 26F2EE549E1BAE4979E15A432DBB63FC5148B31C | 0.2.9.11 | 443 | 80 | Unnamed | NULL | +---------------------+------------------------------------------+-------------+---------+----------+----------+---------+
ornetradar@riseup.net:
2018-01-16
| Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | |------+-------+------------+----------------+------+-------+--------+-----------+-----------+------------+---------------| | 1 | 0 | 00:16:46 | 138.197.99.49 | us | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 01:09:43 | 165.227.25.219 | us | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:07:50 | 178.62.240.100 | nl | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:11:33 | 159.89.192.117 | sg | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:15:04 | 178.62.33.87 | gb | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:53:44 | 139.59.135.196 | de | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:56:53 | 165.227.38.141 | ca | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 03:00:57 | 139.59.89.46 | in | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 |
On Wed, January 17, 2018 7:16 am, nusenu wrote:
I propose to reject these new DigitalOcean relays (no contact/MyFamily)
+---------------------+------------------------------------------+-------------+---------+----------+----------+---------+ | first_seen | fingerprint | tor_version | or_port | dir_port | nickname | contact | +---------------------+------------------------------------------+-------------+---------+----------+----------+---------+ | 2018-01-16 01:00:00 | FD94F9A1FB940786691A7B8A266DCA50C6AE28F1 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 02:00:00 | 314E00247E8A661F3FB583275AD3F7B5466EFC99 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | 0DDD78A986EDECA1E6FD36F8C4ACEFBCB95A90D7 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | 3137D94063BA0F5D92BAD71EC4F452CA875D81D3 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 03:00:00 | AF1D8F02C0949E9755C0DF9C6761FBBF7AAB62C2 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | 5C0C3F106C81BDA139DB1B5CD11E3E8E00C2ECF5 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | B901626F9F7CD538B8B7812223F6614B1CFBDD78 | 0.2.9.11 | 443 | 80 | Unnamed | NULL | | 2018-01-16 04:00:00 | 26F2EE549E1BAE4979E15A432DBB63FC5148B31C | 0.2.9.11 | 443 | 80 | Unnamed | NULL | +---------------------+------------------------------------------+-------------+---------+----------+----------+---------+
ornetradar@riseup.net:
2018-01-16
| Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | |------+-------+------------+----------------+------+-------+--------+-----------+-----------+------------+---------------| | 1 | 0 | 00:16:46 | 138.197.99.49 | us | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 01:09:43 | 165.227.25.219 | us | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:07:50 | 178.62.240.100 | nl | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:11:33 | 159.89.192.117 | sg | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:15:04 | 178.62.33.87 | gb | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:53:44 | 139.59.135.196 | de | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 02:56:53 | 165.227.38.141 | ca | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 | | 1 | 0 | 03:00:57 | 139.59.89.46 | in | 443 | 80 | 0.2.9.11 | None | Unnamed | 1 |
-- https://mastodon.social/@nusenu twitter: @nusenu_
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
+1 blacklisted.
cheers.
-- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
"I don't know where I'm going from here, but I promise it won't be boring." - David Bowie
x9p:
+1 blacklisted.
can you elaborate on what you mean with that?
thanks, nusenu
On Wed, January 17, 2018 10:04 am, nusenu wrote:
x9p:
+1 blacklisted.
can you elaborate on what you mean with that?
thanks, nusenu
-- https://mastodon.social/@nusenu twitter: @nusenu_
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
sorry. blocked on my relays.
cheers.
-- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
"I don't know where I'm going from here, but I promise it won't be boring." - David Bowie
x9p:
+1 blacklisted.
can you elaborate on what you mean with that?
sorry. blocked on my relays.
If you mean "dropping all packets coming from and to these IP addresses to your relays" by that, please don't do that. That breaks functionality for tor clients, removal should happen on a directory authority level.
On Wed, January 17, 2018 5:45 pm, nusenu wrote:
x9p:
+1 blacklisted.
can you elaborate on what you mean with that?
sorry. blocked on my relays.
If you mean "dropping all packets coming from and to these IP addresses to your relays" by that, please don't do that. That breaks functionality for tor clients, removal should happen on a directory authority level.
-- https://mastodon.social/@nusenu twitter: @nusenu_
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
not doing DROPS anymore, trying not to hurt clients. StrictNodes, via torrc
cheers.
-- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
"I don't know where I'm going from here, but I promise it won't be boring." - David Bowie
Hi,
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.
Thanks, Iain.
I've also added those relays to the ExcludeNode with the following options:
ExcludeNodes FD94F9A1FB940786691A7B8A266DCA50C6AE28F1,314E00247E8A661F3FB583275AD3F7B5466EFC99,0DDD78A986EDECA1E6FD36F8C4ACEFBCB95A90D7,3137D94063BA0F5D92BAD71EC4F452CA875D81D3,AF1D8F02C0949E9755C0DF9C6761FBBF7AA$ StrictNodes 1
kind regards, Robin
my relay EA4366BCDCA6167B8CFF70E41D8CD1EE9968E445
----- Original message ----- From: Iain Learmonth irl@torproject.org To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] [OrNetRadar] AS: "DigitalOcean, LLC" - 2018-01-16 Date: Fri, 19 Jan 2018 12:52:42 +0000
Hi,
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.
Thanks, Iain.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Email had 1 attachment: + signature.asc 1k (application/pgp-signature)
Robin:
I've also added those relays to the ExcludeNode with the following options:
This is not necessary.
I'll refrain from CC'ing tor-relays in future bad-relays@ emails because apparently it is causing confusions.
regards, nusenu
OK.
Changes reverted. Kind regards, Robin
----- Original message ----- From: nusenu nusenu-lists@riseup.net To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] [OrNetRadar] AS: "DigitalOcean, LLC" - 2018-01-16 Date: Fri, 19 Jan 2018 19:53:00 +0000
Robin:
I've also added those relays to the ExcludeNode with the following options:
This is not necessary.
I'll refrain from CC'ing tor-relays in future bad-relays@ emails because apparently it is causing confusions.
regards, nusenu
tor-relays@lists.torproject.org
-
Iain Learmonth -
nusenu -
Robin -
robink
-
x9p