- tor-relays - lists.torproject.org

FallbackDir maintenance
by Nurtic-Vibe 18 May '18

18 May '18

Due to a disk outtage, the FallbackDir 8C00FA7369A7A308F6A137600F0FA07990D9D451 is currently offline. I will keep you posted with updates. Cheers, Nurtic-Vibe

1 1

lets stop using central big DNS resolvers (Google, Level3, OpenDNS, Quad9, Cloudflare)
by nusenu 18 May '18

18 May '18

Dear Exit Relay Operators, I'd like to invite you to check your exit's DNS resolver by having a look at the following list of exits using resolvers outside their AS (especially if it is Google, OpenDNS, Quad9 or Cloudflare). You can search the list for you contactinfo, relay nickname or relay fingerprint (first 8 characters): https://gist.github.com/nusenu/cb766ff7945fafd9f90ee7f211a2508f#file-tor-dn… I extended the "DNS on Exit Relays" section in the Tor Relay Guide to include specific instructions what is recommended for Tor exit operators with regards to DNS on exit relays. https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#DNSonExitRelays If you found yourself on the list above and changed your DNS to a local (same host or same AS) resolver or found a false-positive, please drop me an email (off-list is also ok). The goal is to be bellow the following thresholds within one year: - not have any single remoteAS entity control more than 10% exit capacity - reduce the overall remoteAS share to bellow 20% exit capacity the longer version of this can be found at: https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca thanks for helping with DNS decentralization on the tor network, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

14 24

The Onion Box v4.2: Web Interface to monitor your Tor node(s)
by Ralph Wetzel 18 May '18

18 May '18

2 2

New upcoming requirement for relays related to Ed25519 support
by nusenu 17 May '18

17 May '18

Dear tor relay operators, we want to inform you that in future*, tor directory authorities will enforce a new security measurement that disallows relays to drop Ed25519 support in case they ever supported it at some point. In practice that means that if you run tor 0.2.7.2-alpha or later you can not downgrade to an older tor version without Ed25519 support anymore. Tor directory authorities will reject such relays in the future. You are safe if you do _not_ downgrade from any tor version >= 0.2.7.2-alpha to a version older than that. We will send a second email to this list once we are near the actual enforcement of this new requirement (which will not be to soon from now). kind regards, nusenu * This will come into effect when the majority of tor directory authorities are on tor 0.3.4.x ticket: https://trac.torproject.org/projects/tor/ticket/20522 -- https://mastodon.social/@nusenu twitter: @nusenu_

2 2

gratitude
by charlie 16 May '18

16 May '18

i just wanted to put this out there. i greatly appreciate what you guys do with the tor network. it's an awesome thing and i know you guys go through a lot to run it and it's appreciated beyond words. i use the tor network all the time now, especially since i live in america and privacy and net neutrality are not regarded as being important and i feel safe only using the tor network. so thank you! maybe one of these days i can contribute to it with my own relay, node, bridge, anything. keep up the good work. you're the warriors of a free and open internet. charlie

3 2

Unusual load returning?
by r1610091651 15 May '18

15 May '18

Hi I've noticed unusual load on the relay. Notice the huge change in load between 3-8 am (CET). Unusual logs: May 14 03:49:44.000 [notice] Circuit handshake stats since last time: 5592/5592 TAP, 40516/40516 NTor. May 14 09:49:44.000 [notice] Circuit handshake stats since last time: 5864/5864 TAP, 58290/58290 NTor. May 14 15:49:44.000 [notice] Circuit handshake stats since last time: 35313/35313 TAP, 72399/72399 NTor. May 14 21:49:44.000 [notice] Circuit handshake stats since last time: 98315/98315 TAP, 77724/77724 NTor. May 15 03:49:44.000 [notice] Circuit handshake stats since last time: *420868*/423426 TAP, 89627/89627 NTor. May 15 09:49:44.000 [notice] Circuit handshake stats since last time: *1362584*/1364077 TAP, 81196/81197 NTor. May 15 15:49:44.000 [notice] Circuit handshake stats since last time: 5488/5488 TAP, 78317/78317 NTor. For info: middle relay (no exit/guard), no directory, running 3.2.10 [image: image.png] Wondering if others experienced it recently? Regards Seb

1 0

[France] Invitation to HACKarnaval, May 17th
by gus 14 May '18

14 May '18

Hello Tor operators from France! Next thursday, May 17th, some Tor Project contributors are going to be at HACKarnaval, in Paris. Come to say 'bonjour' and meet new friends! :) cheers!, gus * * * * HACKarnaval + Tor Meetup - 17 mai au Musée des Arts et Métiers [HACKarnaval!] est un événement ouvert au publique pour célébrer le “hacking” comme une forme de partage des connaissances. Des techniciens, des chercheurs, des artistes et des bricoleurs de tous les coins du monde proposeront des ateliers, des conférences et des expositions. Rejoignez-nous le jeudi 17 mai au Musée des Arts et Métiers, de 11:00 à 21 heures. Venez explorer les mondes socio-techniques du logiciel, de l'électronique ou du wetware, et discuter des changements qu’ils promettent! https://hackarnaval.online Rencontre Tor https://hackarnaval.online/abstracts-fr/tor-meetup.html Musée des Arts et Métiers 60 rue Réaumur, 75003 Paris Métro : Arts et métiers - Entrée libre ! -- PGP: 427F 2D71 7664 D215 378C B412 8BDC 87FB 7215 E189 XMPP/OTR: 62f58f8062da3e48e0aa076f20807ecb1488658e https://gus.computer/

1 0

Strange BGP activity with my node
by Trevor Ellermann 14 May '18

14 May '18

Hi, I just a notification from my data center that someone is trying to hijack the IP of my exit node. Seems like the sort of thing someone might do when trying to attack Tor. I'm in a very remote area with limited access but any suggestions on actions I should take? ==================================================================== Possible Prefix Hijack (Code: 10) ==================================================================== Your prefix: 204.17.32.0/19: Prefix Description: GBLX-US-BGP Update time: 2018-05-09 12:11 (UTC) Detected by #peers: 1 Detected prefix: 204.17.56.42/32 Announced by: AS200005 (Asavie Technologies Limited) Upstream AS: AS200005 (Asavie Technologies Limited) ASpath: 200005 https://torstatus.blutmagie.de/router_detail.php?FP=383d6e34d9bea92e97092b1… Thanks, --Trevor

5 6

Tor Relay Bandwidth Question
by Keifer Bly 14 May '18

14 May '18

Hello, So I have been away from the computer where my relay is running off of for a few days. I have been wanting to check how much data my relay has been receiving during this time. I check it at http://torstatus.blutmagie.de/router_detail.php?FP=db1af6477bb276b6ea5e7213…, but that only shows how many “bytes” have been sent. I am wondering, is there a way to show this in megabytes / gigabytes? Thank you very much.

3 2

Problem with MyFamily config (doesn't work correctly)
by Olaf Grimm 13 May '18

13 May '18

Dear Tor controllers, For some time now I have relays in different locations and with different systems. All relays have the same torrc, except nickname. The following list shows the excerpt from metrics.torproject.org. Hydra1 (5) Hydra2 (5) Hydra5 (6) Hydra3 (2) Hydra4 (5) Hydra (5) Some time ago I checked all the torrc exactly, if the MyFamily config is correct. All relays have been restarted. Again today. I expect that the number in brackets is equal for all relays in the group. Part of my torrc: (the same for all relays (exerpt nickname), including the own fingerprint) # Hydra MyFamily $E9A31E7EFF7A062AA67DA601CC70605AACF9F385 # Hydra1 MyFamily $0647C3F8352BBFA0D57A1C3E0DCF67FC3E073D2C # Hydra2 MyFamily $B16D271047B18D29F62AE9F3CFC7094258506A03 # Hydra3 MyFamily $A766BF5C5AF7F897D81BD98797B17B1E8C014650 # Hydra4 MyFamily $2D919C1E0DFA4D7760471F971C2CA96E383AEBE0 # Hydra5 MyFamily $3E76E15E6BE6CFF409D44CCC40281AB5BB0B61C2 In the Tor Manual I've found "MyFamily fingerprint,fingerprint,… This option can be repeated many times, for convenience in defining large families: all fingerprints in all MyFamily lines are merged into one list. " With fewer relays in the past I had the variant "MyFamily $KeyID_1,$KeyID_2,$KeyID_3,...". Now this line is longer than the screen is wide. That's why I changed the spelling according the dokumentation. Why does it seem to work in one place while misrepresenting other configs? The correctly displayed one was added last week. Do I interpret the documentation incorrectly that this spelling is possible? How long is the update cycle of the metrics? I think one hour. Nothing happened for days. Now the metrics registered the restart of the relays 1:45h before, but still with the wrong MyFamily ad. Hydra1 (5) 1h 47m Hydra2 (5) 1h 44m Hydra5 (6) 1h 36m Hydra3 (2) 1h 40m Hydra4 (5) 1h 37m Hydra (5) 1h 51m Olaf

2 1