This page uses content from Wikipedia and is licensed under CC BY-SA.

HTTPS Everywhere

HTTPS Everywhere
HTTPS Everywhere icon.svg
Developer(s) Electronic Frontier Foundation and The Tor Project
Stable release
2018.6.21 / 21 June 2018; 35 days ago (2018-06-21)[1][2]
Repository Edit this at Wikidata
Written in JavaScript, Python
Platform Firefox for Android
Google Chrome
Mozilla Firefox
Opera
Type Browser extension
License GNU GPL v3+ (most code is v2 compatible)[3]
Website eff.org/https-everywhere
As of April 2014

HTTPS Everywhere is a free and open-source browser extension for Google Chrome, Mozilla Firefox, Opera, and Firefox for Android, which is 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 "Block all HTTP requests" makes it possible to block and unblock all non-https browser-connections with one click.[6]

Development

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.[9] 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 Google 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 3th 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 [www.https-rulesets.org] was build 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 inventing this feature there are still bundled rulesets shipped within app-updates.

Reception

Two studies have recommended building in HTTPS Everywhere functionality into Android browsers.[20][21] In 2012, Eric Phetteplace described it as "perhaps the best response to Firesheep-style attacks available for any platform".[22] 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.[23]

See also

References

  1. ^ "Changelog.txt". Electronic Frontier Foundation. Retrieved 16 April 2018. 
  2. ^ "Releases · EFForg/https-everywhere". GitHub. Retrieved 16 April 2018. 
  3. ^ HTTPS Everywhere Development Electronic Frontier Foundation
  4. ^ "HTTPS Everywhere | Electronic Frontier Foundation". Eff.org. Retrieved 2014-04-14. 
  5. ^ "HTTPS Everywhere reaches 2.0, comes to Chrome as beta - The H Open: News and Features". H-online.com. 2012-02-29. Retrieved 2014-04-14. 
  6. ^ HTTPS Everywhere Changelog (englisch)
  7. ^ "Automatic web encryption (almost) everywhere - The H Open Source: News and Features". H-online.com. 2010-06-18. Archived from the original on 2010-06-23. Retrieved 2014-04-15. 
  8. ^ Kate Murphy: New hacking tools pose bigger threats to Wi-Fi users. The New York Times, February 17, 2011.
  9. ^ "HTTPS Everywhere | Electronic Frontier Foundation". Eff.org. Retrieved 2014-06-04. 
  10. ^ "HTTPS Everywhere Rulesets | Electronic Frontier Foundation". Eff.org. 2014-01-24. Retrieved 2014-05-19. 
  11. ^ "HTTPS Everywhere Atlas". eff.org. Retrieved 2014-05-24. .
  12. ^ Mills, Elinor (2010-06-18). "Firefox add-on encrypts sessions with Facebook, Twitter". CNET. Retrieved 2014-04-14. 
  13. ^ Scott Gilbertson (2011-08-05). "Firefox Security Tool HTTPS Everywhere Hits 1.0 | Webmonkey". WIRED. Retrieved 2014-04-14. 
  14. ^ a b "HTTPS Everywhere & the Decentralized SSL Observatory | Electronic Frontier Foundation". Eff.org. 2012-02-29. Retrieved 2014-06-04. 
  15. ^ Brian, Matt (2014-01-27). "Browsing on your Android phone just got safer, thanks to the EFF". Engadget.com. Retrieved 2014-04-14. 
  16. ^ Lemos, Robert (2011-09-21). "EFF builds system to warn of certificate breaches | Encryption". InfoWorld. Retrieved 2014-04-14. 
  17. ^ Vaughan, Steven J. (2012-02-28). "New 'HTTPS Everywhere' Web browser extension released". ZDNet. Retrieved 2014-04-14. 
  18. ^ "1 SSAC Advisory on Internal Name Certificates" (PDF). ICANN Security and Stability Advisory Committee (SSAC). 15 March 2013. 
  19. ^ "https-everywhere now delivers new rulesets without upgrading extension". bleepingcomputer.com. 5 April 2018. 
  20. ^ 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 2013-01-08. 
  21. ^ Davis, B.; Chen, H. (2013). "Retro Skeleton". Proceedings of the 11th annual international conference on Mobile systems, applications, and services - Mobi Sys '13. p. 181. doi:10.1145/2462456.2464462. ISBN 9781450316729. 
  22. ^ Kern, M. Kathleen, and Eric Phetteplace. "Hardening the browser." Reference & User Services Quarterly 51.3 (2012): 210-214. [eprints.rclis.org]
  23. ^ Toubiana, Vincent; Verdot, Vincent (2011). "Show Me Your Cookie And I Will Tell You Who You Are". arXiv:1108.5864Freely accessible [cs.CR].