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
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
···
--
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
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.
Thanks for your consideration
Sebastian
···
On 1. Jun 2026, at 20:19, nusenu via tor-relays <tor-relays@lists.torproject.org> wrote:
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.
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
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
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.
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]
There is a time for this, but "now" is a poor choice.
When a release goes EOL, we have a period where we can work with other people and partners, who are in contact with us, about their use of Tor. During this time, we can hint to them at upgrading. Some of the reasons for upgrading are new features, safety, and security issues. We are not in a hurry at all here.
Getting them to upgrade is a goal we all should share, but screwing over their userbase shouldn't be.
Cheers,
Alex
···
On 01/06/2026 20.19, nusenu via tor-relays wrote:
- 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
--
Alexander Hansen Færøy
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
I have started a discussion among dirauth operators on how to deal with
relays who are actively harming outdated clients like that.
As someone who advocated for many years that the torproject and tor
directory authorities should take a stronger stance on relays without proper
family configuration I really appreciate if tor directory authorities would finally
be more active and take actions against such relays.
That would be unexpected and surprising but a very welcome and positive outcome.
Please do not limit the removal of relays to just relays putting end-of-life tor clients at risk but **also**
include relays that put currently supported tor clients at risk. MyFamily does not support super large groups as you know.
To avoid surprising relay operators I would suggest to officially announce that change in actually enforced policy
because operators are not used to it since many run relays in their current configuration since a long time
and directory authorities never did take any actions against them.
I've been in contact with one large operator that would be affected and they confirmed that they will update their configuration soon.
In OrNetStats I had(*) a dedicated section for relay groups that have an actual chance to perform end-to-end correlation attacks:
Operators are only listed if they actually have a chance to do end-to-end correlation attacks, that is:
- their guard and exit probability is > 0%
- they did not properly configure MyFamily
- they run in more than a single /16 network block
(*) unfortunatelly onionoo data quality is still not back to how it used to be before the CollecTor/collector-rs change on 2026-04-02,
therefore OrNetStats has not been updated since March 2026 because it depends on collector and onionoo data.
kind regards,
nusenu
···
--
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
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.
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
···
On 1. Jun 2026, at 20:19, nusenu via tor-relays <tor- >>> relays@lists.torproject.org> wrote:
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org