You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -47,6 +48,8 @@ If you get stuck we have two publicly-archived mailing lists: the https-everywhe
47
48
48
49
You can also find more information on about HTTPS Everywhere on our [FAQ](https://www.eff.org/https-everywhere/faq) page.
49
50
51
+
Also, please remember that this project is governed by [EFF's Public Projects Code of Conduct](https://www.eff.org/pages/eppcode).
52
+
50
53
Thanks again, and we look forward to your contributions!
51
54
52
55
@@ -68,6 +71,20 @@ To submit changes, open a pull request from our [GitHub repository](https://gith
68
71
69
72
HTTPS Everywhere is maintained by a limited set of staff and volunteers. Please be mindful that we may take a while before we're able to review your contributions.
70
73
74
+
## I Want To Fix My Site
75
+
76
+
**"I want to get an SSL certificate"**
77
+
78
+
To get an SSL certificate, as an option, you can go to [Let's Encrypt](https://letsencrypt.org/) and get a free certificate.
79
+
80
+
**"I have an SSL certificate, but it's not configured properly"**
81
+
82
+
Scan your site at the [Mozilla Observatory](https://observatory.mozilla.org/) and get results on what is wrong/insecure about your site, as well as tips and directions on how to fix those issues.
83
+
84
+
**"How do I get on the HSTS Preload list?"**
85
+
86
+
In order to do this, you must have an SSL certificate correctly installed and your site redirecting to HTTPS. As well as meet a few extra requirements for the [`HTTP Strict-Transport-Security`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) header. To view "how close" your site is for HSTS preloading, scan your site [here](https://hstspreload.org/).
87
+
71
88
* * *
72
89
73
90
# Contributing Rulesets
@@ -326,7 +343,7 @@ In `utils` we have a tool called `hsts-prune` which removes `targets` from rules
326
343
327
344
> Let `included domain` denote either a `target`, or a parent of a `target`. Let `supported browsers` include the ESR, Dev, and Stable releases of Firefox, and the Stable release of Chromium. If `included domain` is a parent of the `target`, the `included domain` must be present in the HSTS preload list for all `supported browsers` with the relevant flag which denotes inclusion of subdomains set to `true`. If `included domain` is the `target` itself, it must be included the HSTS preload list for all `supported browsers`. Additionally, if the http endpoint of the `target` exists, it must issue a 3XX redirect to the https endpoint for that target. Additionally, the https endpoint for the `target` must deliver a `Strict-Transport-Security` header with the following directives present:
328
345
>
329
-
> -`max-age` >= 10886400
346
+
> -`max-age` >= 31536000
330
347
> -`includeSubDomains`
331
348
> -`preload`
332
349
>
@@ -372,13 +389,6 @@ We ask that if you want to delete your GitHub account, you either close your HTT
372
389
* * *
373
390
374
391
# Contributing Translations
375
-
376
-
HTTPS Everywhere translations are handled through Transifex. The easiest way to help with translations is to [create a Transifex account](https://www.transifex.com/signup/) if you don't already have one. Then log into your account and click "Explore", then search for "Tor Project", and click on The Tor Project. Then choose the language you plan to translate into, click on the name of that language, and then click "Join team" and "Go" to accept joining the translation team for your language.
377
-
378
-
Then, in the Tor Project resources list, find and click the link for the file
379
-
380
-
HTTPS Everywhere - https-everywhere.dtd
381
-
382
-
and choose "Translate now" to enter the translation interface.
392
+
We are reviewing our process around translations and currently discussing ways to improve. Translations are still processed under the same entity and those who have an account already, do not need to take action at this time. Thank you for your contributions.
0 commit comments