Author: atagar Date: 2014-02-08 19:53:37 +0000 (Sat, 08 Feb 2014) New Revision: 26596 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping 'HTTPS Server Impersonation' Removing the 'HTTPS Server Impersonation' project as per Nick's request. We might add this back in the future if we get a mentor. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2014-02-08 04:00:54 UTC (rev 26595) +++ website/trunk/getinvolved/en/volunteer.wml 2014-02-08 19:53:37 UTC (rev 26596) @@ -425,7 +425,6 @@ <p> <b>Project Ideas:</b><br /> <i><a href="#torCleanup">Tor Codebase Cleanup</a></i><br /> - <i><a href="#httpsImpersonation">HTTPS Server Impersonation</a></i><br /> <i><a href="#chutneyExpansion">Make Chutney Do More, More Reliably</a></i> </p> @@ -972,31 +971,6 @@ </p> </li> - <a id="httpsImpersonation"></a> - <li> - <b>HTTPS Server Impersonation</b> - <br> - Effort Level: <i>Medium to High</i> - <br> - Skill Level: <i>Medium to High</i> - <br> - Likely Mentors: <i>Nick (nickm)</i> - <p> - We have an open proposal for a way to make Tor bridges avoid censorship by - impersonating an HTTPS server. Specifically, we need to hack some popular - SSL "reverse proxy" (your choice) so that it relays regular web connections - to an HTTP server, but certain connections to a local Tor process. <a - href="https://gitweb.torproject.org/torspec.git/blob_plain/HEAD:/proposals/203-https-frontend.txt">Proposal - 203</a> has a general design sketch. - </p> - - <p> - <b>This project is likely trickier than it looks. You should avoid applying - for this if you're uncertain about being able to complete it.</b> - </p> - </li> - </li> - <a id="chutneyExpansion"></a> <li> <b>Make Chutney Do More, More Reliably</b>