aboutsummaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorIan Jackson <ijackson@chiark.greenend.org.uk>2023-11-08 14:15:56 +0000
committerIan Jackson <ijackson@chiark.greenend.org.uk>2023-11-08 14:22:09 +0000
commit33f0ad320b7b0ec66d418807965bf4bc3f21a5d7 (patch)
treed4ca2ae94d48f217098466e222add689da52ef28 /spec
parentbce1d1540d347b57fb1346bf3bd9dc6ab120534b (diff)
downloadtorspec-33f0ad320b7b0ec66d418807965bf4bc3f21a5d7.tar.gz
torspec-33f0ad320b7b0ec66d418807965bf4bc3f21a5d7.zip
Explain why this TLS ciphersuites rule, in non-normative text
Diffstat (limited to 'spec')
-rw-r--r--spec/tor-spec/negotiating-channels.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md
index 74682f4..6a3662e 100644
--- a/spec/tor-spec/negotiating-channels.md
+++ b/spec/tor-spec/negotiating-channels.md
@@ -48,6 +48,10 @@ at least one ciphersuite other than
> This is trivially achieved
> by using any modern TLS implementation,
> and most implementations will not need to worry about it.
+>
+> This requirement distinguishes the current protocol
+> (sometimes called the "in-protocol" or "v3" handshake)
+> from the obsolete v1 protocol.
<a id="tor-spec.txt-2.2"></a>