Author: atagar Date: 2014-02-03 15:33:47 +0000 (Mon, 03 Feb 2014) New Revision: 26582 Modified: website/trunk/getinvolved/en/volunteer.wml Log: Dropping 'HTTPS Everywhere mixed content detection and handling' EFF project done last year as part of OPW. Modified: website/trunk/getinvolved/en/volunteer.wml =================================================================== --- website/trunk/getinvolved/en/volunteer.wml 2014-02-03 15:32:43 UTC (rev 26581) +++ website/trunk/getinvolved/en/volunteer.wml 2014-02-03 15:33:47 UTC (rev 26582) @@ -1163,47 +1163,6 @@ </p> </li> - <a id="httpsEverywhereMixedContentHandling"></a> - <li> - <b>HTTPS Everywhere mixed content detection and handling</b> - <br> - Effort Level: <i>Medium</i> - <br> - Skill Level: <i>Medium</i> - <br> - Likely Mentors: <i>Peter Eckersley (pde), Micah Lee</i> - <p> -Since version 20, Chrome has automatically blocked the loading of insecure -HTTP scripts and CSS in HTTPS pages. Firefox version 23 will do the same. -This is good security practice, but it causes havoc with many sites where -HTTPS Everywhere can secure some, but not all, of the site's content. - </p> - - <p> -Before Firefox 23 launches, we will need a more coherent plan for detecting -sites where we are causing these mixed content situations, and either -disabling or working around the limitation. Failure to do so will mean that -HTTPS Everywhere user experience worsens dramatically when Firefox 23 is -released. Success will mean a dramatic improvement in user experience with -HTTPS Everywhere for Chrome. - </p> - - <b>Critical-path tickets:</b> - - <ul> - <li><a href="https://trac.torproject.org/projects/tor/ticket/6975">6975</a></li> - <li><a href="https://trac.torproject.org/projects/tor/ticket/8664">8664</a></li> - <li><a href="https://trac.torproject.org/projects/tor/ticket/8776">8776</a></li> - </ul> - - <b>Related tickets:</b> - - <ul> - <li><a href="https://trac.torproject.org/projects/tor/ticket/3777">3777</a></li> - <li><a href="https://trac.torproject.org/projects/tor/ticket/6977">6977</a></li> - </ul> - </li> - <a id="httpsEverywhereRulesetTesting"></a> <li> <b>Incorporate Ruleset Testing into the HTTPS Everywhere release process</b>