summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2016-09-26 11:00:08 -0700
committerNick Mathewson <nickm@torproject.org>2016-09-26 11:00:08 -0700
commit97337844b7282946dda12f59bcabc097fad42647 (patch)
tree4ab018e139937eadfe79778f1c3e2f8fc2068e68 /changes
parenta633baf6320291b6f3de15557438682ed7fe2eaa (diff)
parent501fc3bbc6e6e4003c99b0bfd95deb06b2df9580 (diff)
downloadtor-97337844b7282946dda12f59bcabc097fad42647.tar.gz
tor-97337844b7282946dda12f59bcabc097fad42647.zip
Merge branch 'protover_v2_squashed'
Diffstat (limited to 'changes')
-rw-r--r--changes/prop26418
1 files changed, 18 insertions, 0 deletions
diff --git a/changes/prop264 b/changes/prop264
new file mode 100644
index 0000000000..bab8a400e1
--- /dev/null
+++ b/changes/prop264
@@ -0,0 +1,18 @@
+ o Major features (subprotocol versions):
+
+ - Tor now uses "subprotocol versions" to indicate
+ compatibility. Previously, versions of Tor looked at the declared Tor
+ version of a relay to tell whether they could use a given feature.
+ Now, they should be able to rely on its declared subprotocol versions.
+ This change allows compatible implementations of the Tor protocol(s) to
+ exist without declaring compatibility with pretending to be particular
+ releases of Tor itself. Closes ticket 19958; implements part of
+ proposal 264.
+
+ - Tor directory authorities now vote on a set of recommended subprotocol
+ versions, and on a set of required subprotocol versions. Clients and
+ relays that lack support for a _required_ suprotocol version will not
+ start; those that lack support for a _recommended_ subprotocol version
+ will warn the user to upgrade. Closes ticket 19958; implements part of
+ proposal 264.
+