All three of my web tunnels users are dominated by Russian and Iranians This gives a warm glow that I may be doing good
I do worry that a malevolent party could set up a webtunnel and identify originating IP addresses since the webtunnel is, this is for these users, the first way into the system? Perhaps webtunnel providers cannot be anonymous Gerry -----Original Message----- From: Georg Koppen via tor-relays <[email protected]> Sent: 08 June 2026 10:07 To: [email protected] Cc: Georg Koppen <[email protected]> Subject: [tor-relays] Re: relayor v26.2.0 is released - Goodbye "MyFamily" Georg Koppen via tor-relays: > Sebastian Hahn via tor-relays: >> >> >>> On 1. Jun 2026, at 20:19, nusenu via tor-relays <tor- >>> [email protected]> wrote: >>> >>> Hi, >>> >>> relayor v26.2.0 is released. >>> https://github.com/nusenu/ansible-relayor/releases/tag/v26.2.0 >>> >>> This release marks the end of "MyFamily" support in relayor. >>> Since all supported tor versions support the Happy Family design >>> there is no reason to continue supporting the old "MyFamily" method >>> to declare relay families. >>> >>> relayor is an ansible role that helps you with automating tor relay >>> operations >>> https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor- >>> relay-operator >>> >>> Changes since v26.1.0: >>> - remove MyFamily support: The last tor version that required >>> MyFamily (0.4.8.x) in addition to Happy Family support reached end- >>> of-life on 2026-06-01 >>> - use absolute filter name to fix error "No filter named 'ipaddr'" >>> >>> kind regards, >>> nusenu >> >> Hi nusenu, >> >> I am not a fan of breaking security for clients not running the >> latest supported release, while those clients continue to work on the >> network. >> I have started a discussion among dirauth operators on how to deal >> with relays who are actively harming outdated clients like that. >> >> I appreciate your eagerness to push forward, but would argue the harm >> caused by removing MyFamily across the board is greater than keeping >> it around for some time. There are already network team plans to >> break compatibility with an update which would actually mean old >> clients refuse to function, which IMO is much better than breaking >> security silently. > > To add to that: there is a transition process as always when a Tor > version goes EOL. We've been done that several times in the past and > that should not be anything new. Moreover, as Sebastian indicated, we > have this time a hard break for 0.4.8.x clients as well, which is > publicly documented in Gitlab[1] and scheduled for 2026-09-01. By then > 0.4.8.x relays will likely be blocked from the network as well. Thus, > supporting MyFamily until then seems like a good choice to me to avoid > at least confusion among relay operators, in particular as we link to > your tool and talk about setting up MyFamily in the post-install > section of our community portal.[2] > > I'd suggest you reconsider just pulling the plug. @nusenu: is there any progress on that? We now had one dir-auth operator, folks from the network and network-health team weighting in and suggesting that your change was well-intentioned but rushed. It would be nice if you could update relayor accordingly. Thanks, Georg > Georg > > [1] > https://gitlab.torproject.org/tpo/network-health/team/-/work_items/460 > [2] https://community.torproject.org/relay/setup/post-install/ > > _______________________________________________ > tor-relays mailing list -- [email protected] To > unsubscribe send an email to [email protected] _______________________________________________ tor-relays mailing list -- [email protected] To unsubscribe send an email to [email protected]
