commit 5ba6f2e3ed93007c573bcd22ca55cc9afa6ba29e Author: Roger Dingledine arma@torproject.org Date: Tue Sep 20 11:00:35 2011 -0400

trivial fixes to prop 176 --- proposals/176-revising-handshake.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/176-revising-handshake.txt b/proposals/176-revising-handshake.txt index 8ede6cb..39f4465 100644 --- a/proposals/176-revising-handshake.txt +++ b/proposals/176-revising-handshake.txt @@ -231,7 +231,7 @@ Supersedes: 169 accept v2 certificates.

Fortunately, current certificates have a few characteristics that - make them fairly mannered as it is. We say that a certificate + make them fairly well-mannered as it is. We say that a certificate indicates a V2-only server if ALL of the following hold: * The certificate is not self-signed. * There is no DN field set in the certificate's issuer or @@ -280,7 +280,7 @@ Supersedes: 169 On learning the link protocol, the server then sends the client a CERT cell and a NETINFO cell. If the client wants to authenticate to the server, it sends a CERT cell, an AUTHENTICATE - cell, and a NETINFO cell, or it may simply send a NETINFO cell if + cell, and a NETINFO cell; or it may simply send a NETINFO cell if it does not want to authenticate.

The CERT cell describes the keys that a Tor instance is claiming