summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-08-14 09:03:16 +0000
committerRoger Dingledine <arma@torproject.org>2006-08-14 09:03:16 +0000
commitc2c88715c18d2f97ca0365e7b9209950966c6acf (patch)
treee3a7fa9ca71fd707c0ba96612d166d55c7636ad7
parent9b10f11d39457dff322d0f03995ae7d75ca06983 (diff)
downloadtor-c2c88715c18d2f97ca0365e7b9209950966c6acf.tar.gz
tor-c2c88715c18d2f97ca0365e7b9209950966c6acf.zip
clarify that some old versions used an organizationName of "Tor",
and others used "TOR". We should avoid both now. svn:r7050
-rw-r--r--doc/tor-spec.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 1082bbf568..087bbf3a37 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -173,10 +173,10 @@ when do we rotate which keys (tls, link, etc)?
certificate is the OR's nickname, followed by a space and the string
"<identity>".
- Implementations running 0.1.2.0-alpha and earlier used an organizationName
- of Tor. Current implementations (which support the version negotiation
- protocol in section 4.1) MUST NOT have this value for their
- organizationName.
+ Implementations running 0.1.2.0-alpha and earlier used an
+ organizationName of "Tor" or "TOR". Current implementations (which
+ support the version negotiation protocol in section 4.1) MUST NOT
+ have either of these values for their organizationName.
All parties receiving certificates must confirm that the identity key is
as expected. (When initiating a connection, the expected identity key is