Remove the timestamp from AUTHENTICATE cells; replace with random bytes

This isn't actually much of an issue, since only relays send
AUTHENTICATE cells, but while we're removing timestamps, we might as
well do this too.

Part of proposal 222.  I didn't take the approach in the proposal of
using a time-based HMAC, since that was a bad-prng-mitigation hack
from SSL3, and in real life, if you don't have a good RNG, you're
hopeless as a Tor server.

1 files changed, 5 insertions, 3 deletions

diff --git a/changes/no_client_timestamps_024 b/changes/no_client_timestamps_024
index fe8f41927..9ded8b3d9 100644
--- a/changes/no_client_timestamps_024
+++ b/changes/no_client_timestamps_024
@@ -3,8 +3,10 @@
       not used for anything, and they provided one small way for clients
       to be distinguished from each other as they moved from network to
       network or behind NAT. Implements part of proposal 222.
-    - Clients now round timestamps in INTRODUCE2 cells to the nearest
+    - Clients now round timestamps in INTRODUCE2 cells down to the nearest
       10 minutes.  If a new Support022HiddenServices option is set to 0,
       or if it's set to "auto" and the feature is disabled in the consensus,
-      the timestamp is sent as 0 instead.
-
+      the timestamp is sent as 0 instead. Implements part of proposal 222.
+    - Stop sending timestamps in AUTHENTICATE cells. This is not such
+      a big deal from a security point of view, but it achieves no actual
+      good purpose, and isn't needed. Implements part of proposal 222.