summaryrefslogtreecommitdiff
path: root/changes/ticket40162
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-10-23 11:23:08 -0400
committerNick Mathewson <nickm@torproject.org>2020-10-23 11:23:08 -0400
commitfd58e74ddcb012892bd7e59ef1587fc4faa2ab35 (patch)
treedcabea9210c5a9749b3e777c3107035c60c597aa /changes/ticket40162
parentd872c6925516a571b0ce624e913b620ba9324740 (diff)
downloadtor-fd58e74ddcb012892bd7e59ef1587fc4faa2ab35.tar.gz
tor-fd58e74ddcb012892bd7e59ef1587fc4faa2ab35.zip
Update required/recommended protocol lists more systematically
First I began with a set of candidates: The client's _required_ list starts with all the protocols supported by every release in 0.2.9-stable through current master. The client's _required_ list starts with all the protocols supported by every release in 0.3.5-stable through current master. Everybody's _recommended_ list starts with all the protocols supported by every release in 0.3.5-stable through current master. Then I removed the protocol versions that we do not actually want to require or recommend: DirCache=1 (deprecated) HSDir=1, HSIntro=1-3, HSRend=1 (deprecated) (All HS* protocol requirements for clients) Link=1-3 (deprecated) LinkAuth=1 (obsolete) Relay=1 (obsolete)
Diffstat (limited to 'changes/ticket40162')
-rw-r--r--changes/ticket4016210
1 files changed, 5 insertions, 5 deletions
diff --git a/changes/ticket40162 b/changes/ticket40162
index 5a8a76bfd8..093042f9af 100644
--- a/changes/ticket40162
+++ b/changes/ticket40162
@@ -1,7 +1,7 @@
o Minor features (authorities):
- - Authorities now list the directory formats used by currently supported
- Tor releases as required. Previously, they listed only the formats
- supported by older Tor releases as required. This change makes
- the subprotocols "Cons=2 Desc=2 Microdesc=2" required, and makes
- "Cons=1 Desc=1 Microdesc=1" no longer required or recommended.
+ - Authorities now list a different set of protocols as required and
+ recommended. These lists are chosen so that only truly recommended
+ and/or required protocols are included, and so that clients using 0.2.9
+ or later will continue to work (even though they are not supported),
+ whereas only relays running 0.3.5 or later will meet the requirements.
Closes ticket 40162.