HTTPS Everywhere

HTTPS Everywhere was inspired by Google's increased use of HTTPS[7] and is designed to force the usage of HTTPS automatically whenever possible.[8] The code, in part, is based on NoScript's HTTP Strict Transport Security implementation, but HTTPS Everywhere is intended to be simpler to use than NoScript's force HTTPS functionality which requires the user to manually add websites to a list.[4] The EFF provides information for users on how to add HTTPS rulesets to HTTPS Everywhere,[9] and information on which websites support HTTPS.[10]

The SSL Observatory is a feature in HTTPS Everywhere introduced in version 2.0.1[13] which analyzes public key certificates to determine if certificate authorities have been compromised,[15] and if the user is vulnerable to man-in-the-middle attacks.[16] In 2013, the ICANN Security and Stability Advisory Committee (SSAC) noted that the data set used by the SSL Observatory often treated intermediate authorities as different entities, thus inflating the number of certificate authorities. The SSAC criticized SSL Observatory for potentially significantly undercounting internal name certificates, and noted that it used a data set from 2010.[17]

The update to Version 2018.4.3, shipped 3 April 2018, introduces the "Continual Ruleset Updates" function.[18] To apply up-to-date https-rules, this update function executes one rule-matching within 24 hours. A website called https://www.https-rulesets.org/ was built by the EFF for this purpose. This automated update function can be disabled in the add-on settings. Prior the update- mechanism there have been ruleset-updates only through app-updates. Even after this feature was implemented there are still bundled rulesets shipped within app-updates.

Two studies have recommended building in HTTPS Everywhere functionality into Android browsers.[19][20] In 2012, Eric Phetteplace described it as "perhaps the best response to Firesheep-style attacks available for any platform".[21] In 2011, Vincent Toubiana and Vincent Verdot pointed out some drawbacks of the HTTPS Everywhere add-on, including that the list of services which support HTTPS needs maintaining, and that some services are redirected to HTTPS even though they are not yet available in HTTPS, not allowing the user of the extension to get to the service.[22] Other criticisms are that users may be misled to believe that if HTTPS Everywhere does not switch a site to HTTPS, it is because it does not have an HTTPS version, while it could be that the site manager has not submitted an HTTPS ruleset to the EFF.[23] Besides, the connection to the SSL Observatory could be used to track the sites that the user visits.[23]

HTTPS Everywhere initiative inspired opportunistic encryption alternatives :

• 2020: Firefox builtin HTTPS Only Mode.[24][25]
• 2019: HTTPZ[26] for Firefox / WebExt supporting browsers.
• 2017: Smart-HTTPS (closed-source early since v0.2[27]),

• Brave - An open-source browser that integrates HTTPS Everywhere
• Transport Layer Security (TLS) – Cryptographic protocols that provide communications security over a computer network.
• Privacy Badger – A free browser extension created by the EFF that blocks advertisements and tracking cookies.
• Switzerland (software) – An open-source network monitoring utility developed by the EFF to monitor network traffic.
• Let's Encrypt – A free automated X.509 certificate authority designed to simplify the setup and maintenance of TLS encrypted secure websites.
• HTTP Strict Transport Security – A web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking.