HTTPS Everywhere

HTTPS Everywhere
Developer(s)Electronic Frontier Foundation and The Tor Project
Final release
2022.5.24 / May 25, 2022; 20 months ago (2022-05-25)[1][2]
Repository
Written inJavaScript, Python
PlatformFirefox for Android
Google Chrome
Mozilla Firefox
Opera
Vivaldi
Microsoft Edge
TypeBrowser extension
LicenseGNU GPL v3+ (most code is v2 compatible)[3]
Websitewww.eff.org/https-everywhere
As ofApril 2014

HTTPS Everywhere is a discontinued free and open-source browser extension for Google Chrome, Microsoft Edge, Mozilla Firefox, Opera, Brave, Vivaldi and Firefox for Android, which was developed collaboratively by The Tor Project and the Electronic Frontier Foundation (EFF).[4] It automatically makes websites use a more secure HTTPS connection instead of HTTP, if they support it.[5] The option "Encrypt All Sites Eligible" makes it possible to block and unblock all non-HTTPS browser connections with one click.[6] Due to the widespread adoption of HTTPS on the World Wide Web, and the integration of HTTPS-only mode on major browsers, the extension was retired in January 2023.[7]

Development

HTTPS Everywhere was inspired by Google's increased use of HTTPS[8] and is designed to force the usage of HTTPS automatically whenever possible.[9] 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 No Script's forced 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,[10] and information on which websites support HTTPS.[11]

Platform support

A public beta of HTTPS Everywhere for Firefox was released in 2010,[12] and version 1.0 was released in 2011.[13] A beta for Chrome was released in February 2012.[14] In 2014, a version was released for Android phones.[15]

SSL Observatory

The SSL Observatory is a feature in HTTPS Everywhere introduced in version 2.0.1[14] which analyzes public key certificates to determine if certificate authorities have been compromised,[16] and if the user is vulnerable to man-in-the-middle attacks.[17] 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.[18]

Continual Ruleset Updates

The update to Version 2018.4.3, shipped on 3 April 2018, introduces the "Continual Ruleset Updates" function.[19] To apply up-to-date https-rules, this update function executes one rule-matching within 24 hours. A website called https-rulesets was built by the EFF for this purpose.[20] This automated update function can be disabled in the add-on settings. Prior to 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.

Reception

Two studies have recommended building HTTPS Everywhere functionality into Android browsers.[21][22] In 2012, Eric Phetteplace described it as "perhaps the best response to Firesheep-style attacks available for any platform".[23] 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.[24] 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,[25] and that because the extension sends information about the sites the user visits to the SSL Observatory, this could be used to track the user.[25]

Legacy

HTTPS Everywhere initiative inspired opportunistic encryption alternatives:

See also

References

  1. ^ "Changelog.txt". Electronic Frontier Foundation. Retrieved 27 June 2019.
  2. ^ "Releases · EFForg/https-everywhere". GitHub. Retrieved 16 June 2018.
  3. ^ HTTPS Everywhere Development Electronic Frontier Foundation
  4. ^ a b "HTTPS Everywhere". Electronic Frontier Foundation. Retrieved 14 April 2014.
  5. ^ "HTTPS Everywhere reaches 2.0, comes to Chrome as beta". H-online.com. 29 February 2012. Retrieved 14 April 2014.
  6. ^ "HTTPS Everywhere Changelog".
  7. ^ Update on HTTPS Everywhere, Electronic Frontier Foundation, 12 January 2023, retrieved 12 January 2023
  8. ^ "Automatic web encryption (almost) everywhere - The H Open Source: News and Features". H-online.com. 18 June 2010. Archived from the original on 23 June 2010. Retrieved 15 April 2014.
  9. ^ Murphy, Kate (16 February 2011). "New Hacking Tools Pose Bigger Threats to Wi-Fi Users". The New York Times.
  10. ^ "HTTPS Everywhere Rulesets". Electronic Frontier Foundation. 24 January 2014. Retrieved 19 May 2014.
  11. ^ "HTTPS Everywhere Atlas". Electronic Frontier Foundation. Retrieved 24 May 2014.
  12. ^ Mills, Elinor (18 June 2010). "Firefox add-on encrypts sessions with Facebook, Twitter". CNET. Retrieved 14 April 2014.
  13. ^ Gilbertson, Scott (5 August 2011). "Firefox Security Tool HTTPS Everywhere Hits 1.0". Wired. Retrieved 14 April 2014.
  14. ^ a b Eckersley, Peter (29 February 2012). "HTTPS Everywhere & the Decentralized SSL Observatory". Electronic Frontier Foundation. Retrieved 4 June 2014.
  15. ^ Brian, Matt (27 January 2014). "Browsing on your Android phone just got safer, thanks to the EFF". Engadget. Retrieved 14 April 2014.
  16. ^ Lemos, Robert (21 September 2011). "EFF builds system to warn of certificate breaches". InfoWorld. Retrieved 14 April 2014.
  17. ^ Vaughan, Steven J. (28 February 2012). "New 'HTTPS Everywhere' Web browser extension released". ZDNet. Retrieved 14 April 2014.
  18. ^ "1 SSAC Advisory on Internal Name Certificates" (PDF). ICANN Security and Stability Advisory Committee (SSAC). 15 March 2013.
  19. ^ Abrams, Lawrence (5 April 2018). "HTTPS Everywhere Now Delivers New Rulesets Without Upgrading Extension". BleepingComputer.
  20. ^ www.https-rulesets.org https://www.https-rulesets.org/. Retrieved 12 September 2022. {cite web}: Missing or empty |title= (help)
  21. ^ Fahl, Sascha; et al. "Why Eve and Mallory love Android: An analysis of Android SSL (in)security" (PDF). Proceedings of the 2012 ACM Conference on Computer and Communications Security. ACM, 2012. Archived from the original (PDF) on 8 January 2013.
  22. ^ Davis, Benjamin; Chen, Hao (2013). "Retro Skeleton". Proceedings of the 11th annual international conference on Mobile systems, applications, and services - Mobi Sys '13 (published June 2013). pp. 181–192. doi:10.1145/2462456.2464462. ISBN 9781450316729. S2CID 668399.
  23. ^ Kern, M. Kathleen, and Eric Phetteplace. "Hardening the browser." Reference & User Services Quarterly 51.3 (2012): 210-214. http://eprints.rclis.org/16837/
  24. ^ Toubiana, Vincent; Verdot, Vincent (2011). "Show Me Your Cookie And I Will Tell You Who You Are". arXiv:1108.5864 [cs.CR].
  25. ^ a b "Time to stop recommending HTTPS Everywhere? : privacytoolsIO". 28 January 2017.
  26. ^ "Firefox Focus on Android now includes an HTTPS-only mode". Engadget. 8 March 2022. Retrieved 24 December 2022.
  27. ^ "Firefox for Android now has a toggle for HTTPS-Only mode - gHacks Tech News". gHacks Technology News. 29 April 2022. Retrieved 24 December 2022.
  28. ^ Bradshaw, Kyle (29 June 2021). "Google Chrome to offer 'HTTPS-Only Mode'". 9to5Google. Retrieved 13 September 2022.
  29. ^ "Google Chrome will get an HTTPS-Only Mode for secure browsing". BleepingComputer. Retrieved 13 September 2022.
  30. ^ Kerschbaumer, Christoph; Gaibler, Julian; Edelstein, Arthur; Merwe, Thyla van der (17 November 2020). "Firefox 83 introduces HTTPS-Only Mode". Mozilla Security Blog. Retrieved 3 December 2020.
  31. ^ "HTTPS Everywhere FAQ". Electronic Frontier Foundation. 7 November 2016. Retrieved 3 December 2020.
  32. ^ claustromaniac (10 October 2020), claustromaniac/httpz, retrieved 3 December 2020
  33. ^ "Smart HTTPS (revived) repository · Issue #12 · ilGur1132/Smart-HTTPS". GitHub. Retrieved 3 December 2020.