https://github.com/dylanirlbeck/https-observatory

Tool for creating and maintaining HTTPS Everywhere rules.
https://github.com/dylanirlbeck/https-observatory

Last synced: 2 days ago
JSON representation

Tool for creating and maintaining HTTPS Everywhere rules.

• Host: GitHub
• URL: https://github.com/dylanirlbeck/https-observatory
• Owner: dylanirlbeck
• Created: 2019-03-31T20:05:41.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2019-05-05T22:19:35.000Z (over 5 years ago)
• Last Synced: 2024-11-14T08:46:34.311Z (2 months ago)
• Language: JavaScript
• Size: 156 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# HTTPS Observatory

This is an automated system for creating and maintaining HTTPS rules.

To run the server, check out all dependencies in `cache`, start the database, and run `node node/server.js`.

See also:

[Installation instructions](./docs/Setup.md)

You probably already know that modern web mostly uses two protocols: plain text (insecure) HTTP and encrypted (secure) HTTPS. Although the percentage of "pages loaded over HTTPS" tripled in the last 5 years from (25% in January 2014 to over ~75% now[Googe][Firefox]), that metric does not account for sites that deploy HTTPS unreliably and we can fix this (see examples). This is caused by many factors, including complexity of existing standards, legacy code bases and CMS or simply laziness of site administrators to ensure all requests are made over HTTPS. One client-side tool that aims to fix this problem is a browser extension HTTPS Everywhere, which relies on a database of rules telling it which requests to rewrite from HTTP to HTTPS and how to do it. Unfortunately, despite large user base (over 3 million extension users across Chrome, Firefox and Opera) many rules are stale because updates are done mostly manually by a small number of volunteers on GitHub. We plan to automate this process and update existing rulesets and create new ones.

This application will be immediately useful to all 3 million HTTPS Everywhere users once we start merging rulesets upstream and will be useful for site administrators interested in securing their services.