- tor-relays - lists.torproject.org

warning in my relay log
by DARKNET.IT 23 Nov '15

23 Nov '15

I have changed server and tor version (from Tor 0.2.6.10 to Tor 0.2.7.5). My relay works but I have this warning: "http status 400 ("Looks like your keypair does not match its older value.") response from dirserver '208.83.223.34:443'. Please correct." This is my relay fingerprint: 59573AB90614D929360C7D9BCBF3313497A22AA2 What means and what I have to do? The keys for me is correct. Thanks for reply

3 2

Actions required after update?
by kingqueen 23 Nov '15

23 Nov '15

Hi That's a hefty changelog for the new stable release of Tor. I'm in awe of and grateful to the developers, as it's all well beyond me. Please could anybody confirm, is there any action required for somebody running the relay on a pretty bog-standard Ubuntu 12.04 Linux dedi, other than sudo apt-get update && sudo apt-get dist-upgrade ? Thank you!

3 3

IP-Echelon complains about claimed infringement
by Riccardo Mori 22 Nov '15

22 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It's almost a week that I am receiving dozens of "Notices of Claimed Infringement" a day from IP-Echelon, all equals, saying that they "are contacting" me "on behalf of Paramount Pictures Corporation (Paramount)" and asking me to remove the film in question that is being shared via bittorent (the port varies each time). The first time I wrote them that the ip address in question is a Tor exit node, I explained briefly what is Tor and that I can't do anything to help them. I also wrote to MyLoc (the ISP) saying pretty much the same. I wrote to IP-Echelon another time but they never replied. Usually I wouldn't care about them but this time MyLoc told me to "fix the problem or" they "will block" my "server". I modified the exit policy so now I am running the reduced one[1] That (in theory) should fix the problem but I would like to avoid the reduced policy. Is there anyone that had the same issues with IP-Echelon and can help me? Usually how do you handle those annoying auto generated reports? Thanks, patacca [1] https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWT+YZAAoJEE1LNuolWAxgl90P/Rq5DCCc4FrrFqqOSKjisJ57 zBVOpzrfDxAG0ArRFWdhUBi8etpvbNtq042mjevVGp3N3p+IPpyl9bKvZWM7ACID BtBnra7WwMEW21BHqKGmzXJ6CG35AdVRUaJMaJXXSaNGNThFh+mXDGm4B8iHUoI3 3vZxiIHG17INY7lZM7RimYA1MKRQAcICldIYaCA2Nwt/n4gbUlZ3OUXmeGbJins/ NZrN98ZOhxeNg93+wk3f5ns1mQk137ZIcsdb+86uyaqDCxGn7fja2/MXBeHBUonM cZcBUSw1SKdY3XbYh6VyHRhRxWfmHeB/e2MLlDiOZbVc5QgGsOkmwmPKFuNA1dvg w5QoXcUSpUh01mxEK0x1IRl5BAD1zya4ZyITxLAr7OXGVx1jifCvkCKq6rDrLzsX XP8hq8w6Hp9GuFr8QrOx08Q6kvAvQjcF59s6/h0P3ehdbLnNaquEgQA86+WDtlNU lON0MnCf5vmZbww0TP5ymhiiZZIy6uilaqfVJry9lXdiXJvu/xeWs1p2VkxlUpaD ySnjFArg8iT5+veZro1ui0tmqseyu2BdEPfAyu86FcrS3wpbvI983aPDZOEpDoJh NaiE5pQCtsxj7moL1pDfHfFfS23aTGerpj9VTXYE9vd/hO8gqZTWCFA7coDZcXQV 0ZdIkA2C4EI7Rd6ui/cS =CxVx -----END PGP SIGNATURE-----

5 4

Tor Weather not working?
by Green Dream 21 Nov '15

21 Nov '15

I took a relay offline 2 days ago and still haven't received a notification from Tor Weather. The preferences page confirms everything is configured, but yet, it doesn't seem to be working for me. I checked the spam folder. Is there someplace to file tickets for this, or some other contact info for the maintainers of this service? I'd be happy to share additional details if someone wants to look into it.

12 15

IP-Echelon complains about claimed infringement
by Riccardo Mori 21 Nov '15

21 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It's almost a week that I am receiving dozens of "Notices of Claimed Infringement" a day from IP-Echelon, all equals, saying that they "are contacting" me "on behalf of Paramount Pictures Corporation (Paramount)" and asking me to remove the film in question that is being shared via bittorent (the port varies each time). The first time I wrote them that the ip address in question is a Tor exit node, I explained briefly what is Tor and that I can't do anything to help them. I also wrote to MyLoc (the ISP) saying pretty much the same. I wrote to IP-Echelon another time but they never replied. Usually I wouldn't care about them but this time MyLoc told me to "fix the problem or" they "will block" my "server". I modified the exit policy so now I am running the reduced one[1] That (in theory) should fix the problem but I would like to avoid the reduced policy. Is there anyone that had the same issues with IP-Echelon and can help me? Usually how do you handle those annoying auto generated reports? Thanks, patacca [1] https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWT+YYAAoJEE1LNuolWAxg07MP/2ssZc9jiotv3+xReoTFs26j lOqTuEJ8dEAhmGig2hMkHwq+VZUhaDOB8OLPkFwUwFJ76PrvTz5j5p9LTYXwdFbE /2t8eeXTabITtQo0aO/t84g8UNRAmv4ZTWua9Z7DtzhLcrspvftTu3eL5rqbQ4v8 yxI55t8rHXH+sQG2K/io+OpRKjJLcMYexJl8PZOFld/AlkVvabwAtjJi5lhQfcmd V7dlckK1oQTWFGdyw9ww0Bsz1P7sjBLabUXuvP5gxdNyb3LB3uQVxL+29j5G+JBX W0JTJS25g52Mc2ggUiWnzUxdEuKf1pxHAy8Lb6CNG16ZGqZFBu/mdzt9yj72uzng ZUp5eanHVVJIzzkF7AviivkPI0RMUoK2FmwWa7/RrY3p97RrNRB+ytq2ky7IenKR cLx7WXPaG90lSYkHjTFpHZ4kRBVCX4Pd2xmQ8V1DOXMNiyTaabEWE58zVBnPrCQ4 QU+vUduWDkw0Lc8n3KZ0YDZfclhgCLn0qFageCmHRg8tlUgsHTySw6HFIDkYS+X3 6HZkkrOWsfjDAS9+6ZPe+/wzG7xIU9t/ObaxZIHPVydlDF8JlS4wdWHbLZYp608t DCk/l954+uVaQmQCBcah+tZr1Z+lxTJhCAh27QT/s/8WM+tYy9wHAmBLtlWACdFB i74TrbaBXGcX5/rplwjO =YDRS -----END PGP SIGNATURE-----

1 0

Fw: new message
by pridgar＠t-online.de 19 Nov '15

19 Nov '15

Hello! New message, please read <http://wclarkandassociates.com/been.php?zjh> pridgar(a)t-online.de

2 1

Abuse messages from IPs marked as rejected in the exit policy
by tor-admin＠torland.me 18 Nov '15

18 Nov '15

Hi all, I am receiving abuse messages for the Torland1 relay for IPs that are blacklisted in the exit policy. For example as https://atlas.torproject.org/#details/E1E922A20AF608728824A620BADC6EFC8CB8C… shows, 62.67.194.0/24 is blocked. But I am getting abuse messages out of this IP range. Can someone explain me how this can happen? Thanks/regards Torland

2 1

New security feature in upcoming tor 0.2.7.x: OfflineMasterKey
by nusenu 18 Nov '15

18 Nov '15

Hi, I'd like to highlight a "new" security feature in the expected upcoming tor stable release: offline master keys I'm posting this here now - before the actual release - because if you upgrade without thinking about this feature your ed25519 master key will be generated the first time tor 0.2.7.x starts up and at that point in time it might be already to late for the - 'master key never touched my online relay' - option. Why are offline master keys better then online master keys? - you can keep the key under your control while using (semi-trusted) hosting providers - impact of relay compromise or seizure is less fatal and limited in time (default worst case: 30days) - the bad guys have to come back every 30 days to steal your keys again The default expiry for signing keys is 30 days but can be configured (torrc). It is also important to note that if you enable this feature your relays need more care (depending on how you configure key expiry). If you forget about it and the signing key expires your relay will shutdown. Something that will be noticed by a relay operator monitoring its relays and bw usage. Even if you are running 0.2.7.x already you can make use of this feature by moving your master key from the relay to an offline system + torrc configuration. Documentation is currently a bit light but s7r is working on improving it. https://trac.torproject.org/projects/tor/ticket/16645 related tor-dev thread: https://lists.torproject.org/pipermail/tor-dev/2015-November/009905.html ansible-relayor will eventually support offline master keys but it will take some time until tor 0.2.7.x reaches all platforms including OpenBSD. A first (unreviewed) poc has been committed in a dedicated branch. https://github.com/nusenu/ansible-relayor/commit/2c4040df7848f382ced02b43f3… Automation is key in making this feature usable (with short key expiry). You might want to consider this feature - especially if you run a significant portion of the tor network.

1 0

unlisted exit relay
by Green Dream 17 Nov '15

17 Nov '15

While visiting https://torstatus.blutmagie.de/ in Tor Browser, I noticed it wasn't detecting the exit node I was being routed through as a relay. Curious, I tried looking up the same IP in both Atlas and Globe, but neither knows of a relay at this IP. The IP of this exit is 104.156.228.115. What scenarios might cause this situation? As a Tor user, should I care? At the very least, it seems desirable to always be able to research the nodes you are using.

2 1

Tor exit node companion
by Eran Sandler 17 Nov '15

17 Nov '15

Hi guys, I had a thought about writing a small Tor exit node companion app. This would be a single executable that does 2 things: - Serve HTTP port 80 traffic on a specific host name and show the standard Tor web page for exit nodes - Serve port 25 (SMTP) and forwards abuse(a)mydomain.com to an address of your choosing Bonus points would be to make sure the HTTP requests serve the latest version of the Tor disclaimer page (so it will automatically take the latest and periodically check that its the latest). It will then replace the various parts (email of the operator etc). I can write it in Go so that its a single rather small executable so that the exit node will only need to run it instead of web server (nginx or something lighter) and an SMTP server (for those pesky automated posts that, like in the case of webiron, are also sent to abuse(a)mydomain.com based on the reserve DNS). Do you think it would be useful? I would sure be happy to run as little processes as possible. Eran

3 4