[or-cvs] [https-everywhere/master 179/291] a README file that explains what this directory is for (also, emphasizing that the existence of these rules doesn't mean that the user accessed or planned to access the sites they mention!)

schoen at torproject.org schoen at torproject.org
Sat Oct 30 00:32:41 UTC 2010


Author: Seth Schoen <schoen at eff.org>
Date: Wed, 13 Oct 2010 00:56:31 -0700
Subject: a README file that explains what this directory is for
Commit: 093dda97ae9021c985282b3cb1410265a331eac3

---
 src/chrome/content/rules/00README |   17 +++++++++++++++++
 1 files changed, 17 insertions(+), 0 deletions(-)
 create mode 100644 src/chrome/content/rules/00README

diff --git a/src/chrome/content/rules/00README b/src/chrome/content/rules/00README
new file mode 100644
index 0000000..486fbfd
--- /dev/null
+++ b/src/chrome/content/rules/00README
@@ -0,0 +1,17 @@
+<!-- 
+This directory contains web site rewriting rules for the
+HTTPS Everywhere software, available from
+https://www.eff.org/https-everywhere
+
+These rules were contributed to the project by users and aim to
+enable routine secure access to as many web different sites as
+possible.  They are automatically installed together with the
+HTTPS Everywhere software.  The presence of these rules does not
+mean that an HTTPS Everywhere user accessed, or intended to
+access, any particular web site.
+
+For information about how to create additional HTTPS Everywhere
+rewriting rules to add support for new sites, please see
+
+https://www.eff.org/https-everywhere/rulesets
+-->
-- 
1.7.1




More information about the tor-commits mailing list