[tor-commits] [obfsproxy/master] Let the server echo the epoch.

[asn@xxxxxxxxxxxxxx]

commit 33e7c8995d2b7b1ea317bd07d7833a8af6f1f6fe
Author: Philipp Winter <phw@xxxxxxxxxxxxxx>
Date:   Tue Mar 4 20:04:45 2014 +0100

    Let the server echo the epoch.
    
    There's no need for the server to determine its own epoch.
---
 doc/scramblesuit/scramblesuit-spec.txt |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/scramblesuit/scramblesuit-spec.txt b/doc/scramblesuit/scramblesuit-spec.txt
index 45a35f5..e9de667 100644
--- a/doc/scramblesuit/scramblesuit-spec.txt
+++ b/doc/scramblesuit/scramblesuit-spec.txt
@@ -71,7 +71,8 @@
     by 3600.  It represents the amount of hours which have passed since the
     epoch.  It is used by the client and the server to prove liveness.  For
     example, the Unix timestamp 1378768086 would map to E = 1378768086 / 3600 =
-    "382991".
+    "382991".  While the client MUST determine E, the server can simply echo
+    the client's E in its response.
 
     The server's handshake message is created analogous to the client.
 
@@ -124,7 +125,8 @@
     by 3600.  It represents the amount of hours which have passed since the
     epoch.  It is used by the client and the server to prove liveness.  For
     example, the Unix timestamp 1378768086 would map to E = 1378768086 / 3600 =
-    "382991".
+    "382991".  While the client MUST determine E, the server can simply echo
+    the client's E in its response.
 
     Client                         Server  Legend:
       |  T | P | M | MAC(T | P | E)  |     T: session ticket



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits