From 003561fa64615ce9d68d5f3c9f7a6d95768b4158 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Wed, 7 Jun 2006 06:53:43 +0000 Subject: [PATCH] the CookieAuthentication section in our spec seems to assume we're still using the v0 control protocol. svn:r6559 --- doc/control-spec.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/control-spec.txt b/doc/control-spec.txt index 8f7a838559..196cf7e7aa 100644 --- a/doc/control-spec.txt +++ b/doc/control-spec.txt @@ -771,6 +771,11 @@ $Id$ file named "control_auth_cookie" into its data directory. To authenticate, the controller must send the contents of this file. + [With the v1 controller protocol, what we really mean is that you should + send the base16 of the contents of this file. Is this it, or is there + more to it? Should we write a control_auth_cookie.asc file too that + makes this step easier for people doing it manually? -RD] + If the 'HashedControlPassword' option is set, it must contain the salted hash of a secret password. The salted hash is computed according to the S2K algorithm in RFC 2440 (OpenPGP), and prefixed with the s2k specifier.