[HTTPS-Everywhere] CA requirement

[Claudio Moretti]

On Fri, May 24, 2013 at 9:38 AM, oneofthem <oneofthem at lavabit.com> wrote:

> Why doesn't https everywhere include sites that use self signed certs?
> Its not like having a CA signed cert makes a site more secure.
>

To the best of my knowledge, it does. Only, probably, no one has written
rules for the websites you have in mind.
These are the rulesets (files) for websites with self-signed certificates
that are already present in HTTPS-Everywhere:

ApplyYourself.xml
Bangor-University-self-signed.xml
CARI.net-self-signed.xml
Digiweb-self-signed.xml
Hearst-Corporation-self-signed.xml
Igalia-self-signed.xml
Indiana-University-self-signed.xml
Logilab-self-signed.xml
Maricopa-Community-Colleges-self-signed.xml
Memset-self-signed.xml
Mozilla-self-signed.xml
Nextag-self-signed.xml
Ohio-State-University-self-signed.xml
Performancing-self-signed.xml
PostgreSQL-self-signed.xml
The-Flirble-Organisation-self-signed.xml
UCSD.edu-self-signed.xml
University-of-Chicago-self-signed.xml
University-of-Stuttgart-self-signed.xml
University-of-Washington-self-signed.xml
USPS-self-signed.xml
Vispa-self-signed.xml
Williams-College-self-signed.xml
XFCE.org-self-signed.xml

Please, feel free to write any ruleset you want to add and submit it here!

For details on how to write rulesets:
https://www.eff.org/https-everywhere/rulesets

For any other information, ask here!

Claudio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20130524/357fd6a4/attachment.html>