[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-relays] Re: Ebury 1.8.3 on two Quetzalcoatl relay servers: timeline, lessons, open questions
- To: tor-relays@xxxxxxxxxxxxxxxxxxxx
- Subject: [tor-relays] Re: Ebury 1.8.3 on two Quetzalcoatl relay servers: timeline, lessons, open questions
- From: copelandhosting--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 12 Nov 2026 20:59:24 -0000
- Cc: copelandhosting@xxxxxxxxx
- In-reply-to: <2374353.iZASKD2KPV@t520>
- List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
- References: <2374353.iZASKD2KPV@t520>
- Reply-to: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays@xxxxxxxxxxxxxxxxxxxx>
- User-agent: HyperKitty on https://lists.torproject.org/
Hello everybody
My exit node has recently been put on the bad relay list. After I reached out about it, I was linked to this mailing list.
My relay is also hosted at BuyVM/FranTech (KVM-97.LV.BUYVM.NET). I didn't find any suspicious bash history entries, no unknown keys, no iptables or nft redirects, no suspicious processes, no suspicious active network connections and no oddly set suid bits like in the OP. So far I didn't notice anything that looked out of place except for the following:
# ==== OUR_POLICY_BEGIN 2026-10-01 ====
ExitPolicy reject *:25
ExitPolicy reject *:465
ExitPolicy reject *:587
ExitPolicy reject *:110
ExitPolicy reject *:143
ExitPolicy reject *:993
ExitPolicy reject *:995
ExitPolicy reject *:3389
ExitPolicy reject *:135
ExitPolicy reject *:137-139
ExitPolicy reject *:445
ExitPolicy accept *:*
# ==== OUR_POLICY_END ====
This block was inserted at the very top of my torrc file as well.
Based on the limited information that I have so far it does in fact look to me as if BuyVM/FranTech just "went rogue" and modified Exit node's torrc files seemingly unannounced. I didn't see any messages about it on FranTech's Client Area, no announcement and no change in allowed ports in BuyVM's exit policy page (https://buyvm.net/acceptable-use-policy/). FranTech should be also be aware of which VMs are running exit nodes as well, since their Acceptable Use Policy requires that you inform them beforehand that you are going to host an exit node on your VM.
Regards,
Ralph Copeland
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx