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
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Please take the time to focus on one ruleset at a time. Some rulesets are older and need more than just s3 bucket pruning. Some may need more test urls or host updates. We have tests that run on each PR submission, but there are ways to locally test if your environment set up.
-- Within the repo, you can test a ruleset file with this command: python3.6 test/rules/src/https_everywhere_checker/check_rules.py test/rules/http.checker.config rules/example-file.xml.
-- This command will run checks against each host and for proper test coverage. Please address error that may appear.
Run test initially to see which hosts currently have issues python3.6 test/rules/src/https_everywhere_checker/check_rules.py test/rules/http.checker.config rules/example-file.xml
Some hosts have issues? Take out and leave a comment about the error the hosts gave
The main host can't be resolved? The ruleset can be removed entirely, commit and push PR.
Activity
zoracon commentedon Dec 18, 2019
Example workflow
python3.6 test/rules/src/https_everywhere_checker/check_rules.py test/rules/http.checker.config rules/example-file.xmlRemove any references to s3 buckets.
Update possible missed subdomains with Sublistr tool or dnsdumpster.com.
Run
check_rules.pytest again to see if any hosts or coverage is needed still.Repeat test until ruleset checks out and push a PR to the forked repo comparing to the master branch of the EFF/Https-Everywhere repo.
zoracon commentedon Mar 5, 2020
Closing for now since this event has passed.