Browse code

coming to us with tlsdate stuff isn't going to make anybody happy

Roger Dingledine authored on23/12/2016 06:11:22
Showing1 changed files
... ...
@@ -247,14 +247,6 @@ meetings around the world.</li>
247 247
         <td>meejah</td>
248 248
       </tr>
249 249
 
250
-      <tr>
251
-        <td><a href="#project-tlsdate">Tlsdate</a></td>
252
-        <td>Utility</td>
253
-        <td>C</td>
254
-        <td>None</td>
255
-        <td>ioerror</td>
256
-      </tr>
257
-
258 250
       <tr>
259 251
         <td><a href="#project-metrics">Metrics</a></td>
260 252
         <td>Client Service</td>
... ...
@@ -602,21 +594,6 @@ meetings around the world.</li>
602 594
     <i><a href="#txtorcon_use_pytest">Convert txtorcon to py.test</a></i>
603 595
     </p>
604 596
 
605
-    <a id="project-tlsdate"></a>
606
-    <h3>Tlsdate (<a href="https://github.com/ioerror/tlsdate">code</a>)</h3>
607
-
608
-    <p>
609
-    tlsdate: secure parasitic rdate replacement
610
-    </p>
611
-
612
-    <p>
613
-    tlsdate sets the local clock by securely connecting with TLS to remote
614
-    servers and extracting the remote time out of the secure handshake. Unlike
615
-    ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
616
-    enabled service, and provides some protection against adversaries that try
617
-    to feed you malicious time information.
618
-    </p>
619
-
620 597
     <a id="project-metrics"></a>
621 598
     <h3><a href="https://metrics.torproject.org/">Metrics</a> (<a
622 599
     href="https://gitweb.torproject.org/metrics-web.git">web</a>)</h3>