[tor-relays] Re: relayor v26.2.0 is released - Goodbye "MyFamily"

[Sebastian Hahn via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>]

> On 1. Jun 2026, at 20:19, nusenu via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> 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.

Thanks for your consideration
Sebastian

_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx