Completely drop support for Tor 0.2.2.x
|Reported by:||nickm||Owned by:|
|Severity:||Normal||Keywords:||tor-relay, tor-auth, 026-triaged-1, unfrozen, 027-triaged-1-out, tor-03-unspecified-201612|
We should remove 0.2.2.x from the recommended version list.
We should stop accepting Tor 0.2.2.x nodes in the network: that release series is completely unsupported.
Finally dropping 0.2.2.x will let us start deprecating things that we'd like to throw away, like the renegotiation-based handshake.
|#11149||Stop listing relays that run Tor 0.2.2|
|#11150||Remove client code for connecting to and using 0.2.2 servers||TvdW|
|#11151||Drop support for 0.2.2 clients|
|#15212||Log link protocol version counts as part of heartbeat|
|#15233||Form a plan for killing off 0.2.2 and 0.2.3||nickm|
|#15760||tortls.c fails to compile with OpenSSL 1.1.0-dev|
Change History (32)
comment:13 Changed 3 years ago by nickm
- Milestone changed from Tor: 0.2.5.x-final to Tor: 0.2.6.x-final
comment:17 Changed 2 years ago by nickm
- Milestone changed from Tor: 0.2.6.x-final to Tor: 0.2.7.x-final
comment:26 Changed 16 months ago by nickm
- Milestone changed from Tor: 0.2.8.x-final to Tor: 0.2.9.x-final
- Severity set to Normal
comment:28 Changed 13 months ago by isabela
- Milestone changed from Tor: 0.2.9.x-final to Tor: 0.2.???