<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Cool idea! I think it's probably not a fit for HTTPS Everywhere,
though. Part of the reason we want everybody to be able to talk
HTTPS with their favorite web sites is that your browsing is
encrypted all the way to the web site, so what you read is just
between you and the sites you visit.<br>
<br>
If we added web.archive.org in the middle as a proxy, (a) the
Archive would know what you're browsing, and (b) someone tapping the
network on the other side of the Archive would know what you're
browsing.<br>
<br>
Proxies are a valid and useful tool for a lot of use cases, but I
think users are better off choosing a full proxy and using the
functionality in their browser.<br>
<br>
Thanks,<br>
Jacob<br>
<br>
<div class="moz-cite-prefix">On 08/14/2014 02:36 AM, Paul Wise
wrote:<br>
</div>
<blockquote cite="mid:1407998171.5351.43.camel@chianamo" type="cite">
<pre wrap="">Hi all,
Possibly crazy idea:
web.archive.org uses https.
web.archive.org has an option to be a proxy to other sites, via the save
URL option.
For sites with only http available, https-everywhere could redirect to
web.archive.org.
This won't work for dynamic websites though but those could be
whitelisted.
Thoughts?
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
HTTPS-Everywhere mailing list
<a class="moz-txt-link-abbreviated" href="mailto:HTTPS-Everywhere@lists.eff.org">HTTPS-Everywhere@lists.eff.org</a>
<a class="moz-txt-link-freetext" href="https://lists.eff.org/mailman/listinfo/https-everywhere">https://lists.eff.org/mailman/listinfo/https-everywhere</a></pre>
</blockquote>
<br>
</body>
</html>