Opened 4 months ago

Last modified 3 months ago

#34357 new task

Reject relays running 0.4.1

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 042-should, 044-deferred
Cc: gk, phw, arma, ggus Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Now that 0.4.1 has reached end-of-life, it's time for directory authorities to stop accepting relays running it.

See #32672 for the last time we did this.

Looking at the graphs, I don't see a significant change in the drop-off rate for deprecated versions in between when we announced that they were deprecated, and when we finally removed them. Maybe this time we should just send out an announcment, wait a month, then reject the relays?

Child Tickets

Change History (4)

comment:1 Changed 4 months ago by nusenu

Sounds good to me. I can send the announcement to tor-relays@

For current 041 fraction see (updated daily):
https://nusenu.github.io/OrNetStats/#major-versions

comment:2 Changed 4 months ago by nickm

Interesting! Yes, I think an announcement would be fine.

Do you think that sending other emails was actually helpful, the last time we did it? Looking at the graphs from the metrics site, I can't see an impact from those.

comment:3 Changed 4 months ago by nusenu

The email to tor-relays and a few operators in BCC has been sent.

Tor end-of-life pre-removal notification for tor 0.4.1.x relays
https://lists.torproject.org/pipermail/tor-relays/2020-June/018594.html

Do you think that sending other emails was actually helpful, the last time we did it? Looking at the graphs from the metrics site, I can't see an impact from those.

To a limited extend, yes. More so if the email comes from a torproject.org email address.

comment:4 Changed 3 months ago by nickm

Keywords: 044-deferred added
Milestone: Tor: 0.4.4.x-finalTor: unspecified

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Note: See TracTickets for help on using tickets.