Opened 5 years ago
Last modified 6 months ago
#15941 assigned task
Form a plan for killing off client versions which assume they'll live forever
Reported by: | teor | Owned by: | |
---|---|---|---|
Priority: | High | Milestone: | Tor: unspecified |
Component: | Core Tor/Tor | Version: | Tor: 0.2.4.1-alpha |
Severity: | Normal | Keywords: | SponsorS, needs-proposal, tor-dos-designs, 034-triage-20180328, 034-removed-20180328 |
Cc: | nickm | Actual Points: | |
Parent ID: | #15940 | Points: | 3 |
Reviewer: | Sponsor: |
Description
From at least 0.2.4 to 0.2.6, tor client versions assume that they will keep on using the network forever. They have no "request to stop" code or other mechanisms that prevent them becoming a drain on the network.
It would help to plan their transition out at some point, so we can work out what to do to make version obsolescence in future.
See #15233 for killing off 0.2.2 and 0.2.3
Child Tickets
Change History (27)
comment:1 Changed 5 years ago by
Type: | defect → task |
---|
comment:2 Changed 4 years ago by
Keywords: | 028-triage added |
---|
comment:3 Changed 4 years ago by
Keywords: | SponsorU removed |
---|---|
Sponsor: | → SponsorU |
comment:4 Changed 4 years ago by
Points: | → medium |
---|---|
Priority: | normal → major |
comment:5 Changed 4 years ago by
Owner: | set to nickm |
---|---|
Status: | new → accepted |
comment:6 Changed 4 years ago by
Milestone: | Tor: 0.2.8.x-final → Chronos: phase two |
---|
We have design proposals here, but not finalized. Need to take another look in 0.2.9
comment:7 Changed 4 years ago by
Milestone: | Chronos: phase two → Tor: 0.2.9.x-final |
---|---|
Severity: | → Normal |
Actually 0.2.9.
comment:8 Changed 4 years ago by
Sponsor: | SponsorU → SponsorU-can |
---|
comment:9 Changed 4 years ago by
Keywords: | tor-dos-designs added |
---|
comment:10 Changed 4 years ago by
Points: | medium → 3 |
---|
comment:11 Changed 3 years ago by
Owner: | nickm deleted |
---|---|
Status: | accepted → assigned |
comment:12 Changed 3 years ago by
Status: | assigned → new |
---|
Put all unowned "assigned" tickets back into "new".
comment:13 Changed 3 years ago by
Sponsor: | SponsorU-can |
---|
comment:14 Changed 3 years ago by
Milestone: | Tor: 0.2.9.x-final → Tor: 0.2.??? |
---|
comment:15 Changed 3 years ago by
Keywords: | 029-OUT added |
---|
comment:17 Changed 3 years ago by
Keywords: | tor-03-unspecified-201612 added |
---|---|
Milestone: | Tor: 0.3.??? → Tor: unspecified |
Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.
comment:18 Changed 3 years ago by
Keywords: | tor-03-unspecified-201612 removed |
---|
Remove an old triaging keyword.
comment:19 Changed 3 years ago by
Keywords: | 028-triage removed |
---|
comment:20 Changed 3 years ago by
Keywords: | 029-OUT removed |
---|
comment:21 Changed 2 years ago by
Milestone: | Tor: unspecified → Tor: 0.3.2.x-final |
---|---|
Owner: | set to nickm |
Status: | new → accepted |
comment:22 Changed 2 years ago by
Milestone: | Tor: 0.3.2.x-final → Tor: 0.3.3.x-final |
---|
comment:23 Changed 22 months ago by
Milestone: | Tor: 0.3.3.x-final → Tor: 0.3.4.x-final |
---|
I don't think we will or can do this in 033.
comment:24 Changed 21 months ago by
Keywords: | 034-triage-20180328 added |
---|
comment:25 Changed 21 months ago by
Keywords: | 034-removed-20180328 added |
---|
Per our triage process, these tickets are pending removal from 0.3.4.
comment:26 Changed 20 months ago by
Milestone: | Tor: 0.3.4.x-final → Tor: unspecified |
---|
These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.
comment:27 Changed 6 months ago by
Owner: | nickm deleted |
---|---|
Status: | accepted → assigned |
I am not actually working on these tickets, so they shouldn't be assigned to me.
Bulk-replace SponsorU keyword with SponsorU field.