[tor-commits] [webwml/master] coming to us with tlsdate stuff isn't going to make anybody happy

[arma at torproject.org]

commit 3c259a44d6dee8b3f6273ae7315a2372c9bf30c7
Author: Roger Dingledine <arma at torproject.org>
Date:   Fri Dec 23 00:11:22 2016 -0500

    coming to us with tlsdate stuff isn't going to make anybody happy
---
 getinvolved/en/volunteer.wml | 23 -----------------------
 1 file changed, 23 deletions(-)

diff --git a/getinvolved/en/volunteer.wml b/getinvolved/en/volunteer.wml
index 8f785db..a645967 100644
--- a/getinvolved/en/volunteer.wml
+++ b/getinvolved/en/volunteer.wml
@@ -248,14 +248,6 @@ meetings around the world.</li>
       </tr>
 
       <tr>
-        <td><a href="#project-tlsdate">Tlsdate</a></td>
-        <td>Utility</td>
-        <td>C</td>
-        <td>None</td>
-        <td>ioerror</td>
-      </tr>
-
-      <tr>
         <td><a href="#project-metrics">Metrics</a></td>
         <td>Client Service</td>
         <td>Java</td>
@@ -602,21 +594,6 @@ meetings around the world.</li>
     <i><a href="#txtorcon_use_pytest">Convert txtorcon to py.test</a></i>
     </p>
 
-    <a id="project-tlsdate"></a>
-    <h3>Tlsdate (<a href="https://github.com/ioerror/tlsdate">code</a>)</h3>
-
-    <p>
-    tlsdate: secure parasitic rdate replacement
-    </p>
-
-    <p>
-    tlsdate sets the local clock by securely connecting with TLS to remote
-    servers and extracting the remote time out of the secure handshake. Unlike
-    ntpdate, tlsdate uses TCP, for instance connecting to a remote HTTPS or TLS
-    enabled service, and provides some protection against adversaries that try
-    to feed you malicious time information.
-    </p>
-
     <a id="project-metrics"></a>
     <h3><a href="https://metrics.torproject.org/">Metrics</a> (<a
     href="https://gitweb.torproject.org/metrics-web.git">web</a>)</h3>