December 2025 - tor-relays - lists.torproject.org

Hetzner Netscan False Positives
by tor_appliedprivacy.net 06 Feb '26

06 Feb '26

Hi, we just wanted to let you know that we got a Hetzner network contact yesterday here at 39C3 to try to get this issue solved at the root. We can not promise anything at this point but we will likely update this thread in a few weeks (January) about the status with Hetzner on this topic. best regards, tor(a)appliedprivacy.net

6 9

upcoming CIISS update
by nusenu 01 Feb '26

01 Feb '26

Hi, I'm working on a new contactinfo information sharing specification version. Current version (2): https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/ Some likely changes will be: * add happy family proof https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/407/diffs * add signal username field https://support.signal.org/hc/en-us/articles/6712070553754-Phone-Number-Pri… * maybe add keyoxide field as suggested by boldsuck: https://github.com/nusenu/ContactInfo-Information-Sharing-Specification/iss… Feel free to send me your suggestions and opinions before 2025-06-30 by creating github issues or by replying to this thread. kind regards, nusenu -- https://nusenu.github.io

3 5

Tor Relay Operator Meetup at 39c3
by Alexander Hansen Færøy 06 Jan '26

06 Jan '26

Hello folks, Leibi has managed to get a spot for a Tor Relay Operator Meetup here at #39c3. Folks can join us on day 3 at 00:00. For more information, check out: https://events.ccc.de/congress/2025/hub/en/event/detail/tor-relay-operators… Cheers, Alex -- Alexander Hansen Færøy

2 2

Relay forest18 is still not on the consensus
by forest-relay-contact＠cryptolab.net 06 Jan '26

06 Jan '26

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello. One of my new relays is simply not showing up on the consensus. It's been a few days already. I ended up wiping /var/lib/tor and restarting in order to get a new fingerprint, but it has been a while and it is still not showing up on the consensus. I have 21 relays, and this one, the 18th, is the only one having this problem. Even the 21st has shown up on the consensus already. The new fingerprint is 6435C5172690160DA25681BEBA1EA5EAC6F2BE70. Is it possible that it has been incorrectly blacklisted due to being mistaken for one of the relays involved in the recent sybil attack? The IP address is 160.250.225.3. What confuses me is that, even after changing fingerprints, it still is not showing up. It is connected to the network and is reachable from the outside. Regards, forest -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvLrj6cuOL+I/KdxYBh18rEKN1gsFAmk1NxEACgkQBh18rEKN 1gtojw/9Hoix29gE4oevhlRJvGLftgbJHv5caZ7iGNZ7KdN7R/8HQ//0InfyG5d4 8Mb49D2jzNfLK+89svlMyNso5ZqR3sMcy7dpnTNAq+PlxB84AwQE/9Qb/8R3sTDZ A2S8ezzCtViQTEQh9eYx+zmnjJckwVt4sAbjumc6t3kIdN+f7CjOj2SZ+AbT6e4l hBZdaGwKLUQhPzL35SK20RSTjIvVNDHAwMo5rR6BsHCj/+W+3fmAG29pieqCAGp/ lwXR6E4EMII0f53Pb65ZB38FOTuMkBBFL0I3WUB90IqS4z+L3U9oU2u7KY1np1lp ApCSbQjoY+NSgpdJ0yH5b1ZZEvEnr1OhQqY0RMpVTLXOuByj79NG31mjE1v8aUaN a5Lwk6scYXuPr8ryOkxkX80tN5V21pIQWt9hubpXBHtPLvfGmTS51DwwOOEKYoIA yyFnVST75f38uyvm73H48s9c68263I5fKQvFCzUmq8Go0lpbLutjxC8LNML3J0cq 0rIINHWKDw4UjnboKihkuoRdXi+tH2ERW3ZAoKVUXTi1VHomwfDvBHJSYxb3SipI 54Qjrnd6IFr8LaHcTfFacrD/OH4WAYnGCE3lC4Ly3xX0P8Cb9KDkop8nXPuBJAup Jq7GgDP8vsmWW6hp4q/Sh+ajHkeZm/luNWA3DZqsp4q0grHi/IM= =Zdqz -----END PGP SIGNATURE-----

7 28

Netscan Hetzner
by Diyar Ciftci 04 Jan '26

04 Jan '26

Good evening, Apologies as this is likely the incorrect way to do things. I'm not fantastic with mailing lists. I saw on tor forum that some people were getting these netscan emails from hetzner. https://forum.torproject.org/t/tor-relays-abuse-report-from-relays-in-famil… I got my first a few months ago and I just got my second one about an hour ago. Both times it was to the 1st amendment group IP addresses. Last time I just clicked their check button and it passed and then I gave reasoning in the next link. For some reason it doesn't seem to be liking when I click the first link this time and keeps saying not solved. I don't know what my best course of action is. I've gotten 2 reports for hetzner for a guard and 0 for netcup for an exit relay :( I saw in the forum post (which is to a clone of the mailing list) about temporarily blocking tor but that feels a bit deceptive so I don't really want to go down that route. The best thing though it may be a long process as there may be a potential harm to how circuits are built negatively affecting user anonymity is for the tor program to operate in a manner so that it doesn't look like a netscan to some sensitive providers like hetzner even though we know it isn't a netscan anyways. If this issue keeps coming up with hetzner I may look at not hosting a tor relay with them because I have a lot of stuff on this server like my personal website and project mirrors and such and don't want those to be negatively affected due to a unjust IP ban by hetzner for running a tor relay. Any advice? Kind regards, Diyar Ciftci

6 10

Questions about running an exit relay
by tor＠rehcamp.de 03 Jan '26

03 Jan '26

Hi dear list, I hope I am in the correct place for my questions regarding my tor setup. I am currently running a guard/middle relay on a vServer. The relay runs inside a docker container, exposing OrPort and DirPort externally and ControlPort and MetricsPort internally. On the same machine, but in different docker networks (except for prometheus for metrics), multiple other containers providing my personal infrastructure are running. All of them run behind caddy, which only forwards requests coming to specific subdomains on a specific domain. First of all: Is this already a bad idea? Do you seperate tor relays and personal infrastructure physically or in VMs instead of containers? Now, as netcup is my provider and they seem to tolerate exit nodes, I am thinking about allowing exits. I assume this would increase visibility of my server and maybe attract more attention. Knowing the IP address of the tor node, it could be possible to find other domains pointing to it (the PTR record however points to an irrelevant entry) and maybe find the subdomains leading to (still login-protected) infra. Do you think this is a reason not to open the relay for exits? I only have a single IPv4 address to use, additional addresses would imply additional costs. However, I do have a /64 block of IPv6 addresses. For IPv6, i could separate the tor address from the address used personally and therefore make it impossible to reach anything except tor over the designated address and covert any other domains, as they won't be associated with the tor address. Do you think this would be needed/enough? In this case, I would restrict the relay to IPv6-only exits. I am sorry if I could have found more information in the docs, but everything that I did find did not answer my questions enough. Kind regards.

5 5

CPU requirement gone up?
by gerard＠bulger.co.uk 31 Dec '25

31 Dec '25

(Linux 6.8.0-90-ge...) Tor 0.4.8.21 (recommended) I used spin up Webtunnels on very cheap VPS, bandwidth and uptime being my main consideration. But in recent days CPU is 99% even at quiet sites with under 50 outgoing connections. This is new. It would run at 30-50% before. Gerry

4 5

abuse report from relays in family 7EAAC49A7840D33B62FA276429F3B03C92AA9327
by Dimitris T. 29 Dec '25

29 Dec '25

Hey all, got an abuse report today from Hetzner concerning one middle relay we're running there. allegedly, our relay has been port scanning (port 443 only) some members of https://metrics.torproject.org/rs.html#search/family:7EAAC49A7840D33B62FA27… (just from family relays in 96.9.98.0/24 range, all using ORPort 443) anyone else got similar abuse reports? or someone here from this relay family, that can clear things out with this isp? thinking of replying to hetzner accordingly, let them know (with metrics link), that these are tor relays with 443 port open/accepting our middle relay connections, not port scans... best, d.

14 29

Consensus frequently reports relay down, despite relay passing traffic
by forest-relay-contact＠cryptolab.net 29 Dec '25

29 Dec '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello. One of my relays, forest19 (E21B4A2C2852298186C0EA7E2F900EF03AE38D69), frequently appears offline in the consensus despite my uptime monitors and bandwidth graphs showing uninterrupted activity. About once a day to once every other day, I get a Tor Weather notice that my relay has been offline for the last 4 hours. The relay is able to ping all authorities but Sarge, and I am not seeing abnormally high packet loss. How do I troubleshoot this? Regards, forest -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvLrj6cuOL+I/KdxYBh18rEKN1gsFAmlN4PQACgkQBh18rEKN 1gtdxg//QENLNjbb8Ukg40Cyd5vaJDw7PSmcS7XKTh1VID6ZrCdw53arHiYBfvZM Ez26SRD+4gj6//Oz+uz2A0jcBJ8fa+RewTwm4WBthiNGLs8hhyt03CN9zA/j/sm0 9VEkxORYAnjTwJmUQYZKIzfF0GdjJirfuk/daq2q5s4Uxd1tspSSTvYI/O/myE+l 7M5qXtu7OSAJynwYGySQPudt9dGgXdb7fDCATaM7gczXpkHFkSxwIrCNHGYPPL+/ Y/xewRs5rHb0TS8DRJcvDKNBSRaTTNLUQkmiRN4it7pY3w/DWkEWduTwvufMsvK3 3AOs75oaO2cs2WVkqQag12uHTtw78uzegObZl9RPaWmThrbQ8SF/co+10zUUlUa9 UXik2zgpAyQzLLb6TNmLAkNAALQUXvO6YZnZ2z6lrkiXW5ySsgmAhgKaPX9JufKz xbXJ2kkyWRt5xP4y/I5tHj+vmjhLjahmn/gy2O3S1atdTwsd5OX0sn1MzdLfsjw2 9DPaCZpvaOCXwHoQFYM5q0K+JqDNrhsgoCMbjnIhrj/J19OCCYoaLPDd4rxrMOJ8 nsl6hzxi6804hol4A9MDnWzNpAxdxFahSbEE523TfG6OaQG4rw2GyP15Ai6NK6fO Am1cgei2NDAZBquFNB7tI2gfGvle+n7boviHdaMNmlEqMhLL7Pk= =hlTa -----END PGP SIGNATURE-----

4 4

Manual calculation of the bridge-moji
by Marek Küthe 28 Dec '25

28 Dec '25

Hello, When I add a bridge in Tor Browser, the fingerprint is displayed with four emojis. I would be interested to know how I can create this fingerprint manually, for example with Ansible or a Python script. The reason for this is that I would like to list my bridges with their fingerprints on my website, preferably with emojis as well. I would appreciate a reply! Best regards, Marek Küthe -- Marek Küthe m.k(a)mk16.de er/ihm he/him

2 1