HTTPS Everywhere

HTTPS Everywhere
Developer(s) The Tor Project and the Electronic Frontier Foundation
Stable release
Firefox: 5.2.5, Chrome: 2016.9.21 / 21 September 2016 (2016-09-21)[1]
Repository gitweb.torproject.org/https-everywhere.git
Development status Active
Written in JavaScript
Type Browser extension
License GNU GPL v3+ (most code is v2 compatible)[2]
Website eff.org/https-everywhere
As of April 2014

HTTPS Everywhere is a free and open source web browser extension for Google Chrome, Mozilla Firefox and Opera, which is developed collaboratively by The Tor Project and the Electronic Frontier Foundation (EFF).[3] It automatically makes websites use the more secure HTTPS connection instead of HTTP, if they support it.[4]

Development

HTTPS Everywhere was inspired by Google's increased use of HTTPS,[5] and is designed to make HTTPS automatically used whenever possible.[6] 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.[7] The EFF provides information for users on how to add HTTPS rulesets to HTTPS Everywhere,[8] and information on which websites support HTTPS.[9]

Platform support

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

SSL Observatory

The SSL Observatory is a feature in HTTPS Everywhere introduced in version 2.0.1[12] which analyzes public key certificates to determine if certificate authorities have been compromised,[14] and if the user is vulnerable to man-in-the-middle attacks.[15] In 2013, the ICANN Security and Stability Advisory Committee (SSAC) noted that the dataset 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.[16]

Reception

Two studies have recommended building in HTTPS Everywhere functionality into Android browsers.[17][18] In 2012, Eric Phetteplace described it as "perhaps the best response to Firesheep-style attacks available for any platform".[19] In 2011, Vincent Toubiana and Vincent Verdot pointed out some drawbacks of the HTTPS Everywhere plugin, 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.[20]

See also

References

  1. ↑ "Changelog.txt". EFF. 2016-09-21. Retrieved 2016-09-24.
  2. ↑ HTTPS Everywhere Development Electronic Frontier Foundation
  3. ↑ "HTTPS Everywhere | Electronic Frontier Foundation". Eff.org. Retrieved 2014-04-14.
  4. ↑ "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.
  5. ↑ "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.
  6. ↑ Kate Murphy: New hacking tools pose bigger threats to Wi-Fi users. The New York Times, February 17, 2011.
  7. ↑ "HTTPS Everywhere | Electronic Frontier Foundation". Eff.org. Retrieved 2014-06-04.
  8. ↑ "HTTPS Everywhere Rulesets | Electronic Frontier Foundation". Eff.org. 2014-01-24. Retrieved 2014-05-19.
  9. ↑ "HTTPS Everywhere Atlas". eff.org. Retrieved 2014-05-24..
  10. ↑ Mills, Elinor (2010-06-18). "Firefox add-on encrypts sessions with Facebook, Twitter". CNET. Retrieved 2014-04-14.
  11. ↑ Scott Gilbertson (2011-08-05). "Firefox Security Tool HTTPS Everywhere Hits 1.0 | Webmonkey". WIRED. Retrieved 2014-04-14.
  12. 1 2 "HTTPS Everywhere & the Decentralized SSL Observatory | Electronic Frontier Foundation". Eff.org. 2012-02-29. Retrieved 2014-06-04.
  13. ↑ Brian, Matt (2014-01-27). "Browsing on your Android phone just got safer, thanks to the EFF". Engadget.com. Retrieved 2014-04-14.
  14. ↑ Lemos, Robert (2011-09-21). "EFF builds system to warn of certificate breaches | Encryption". InfoWorld. Retrieved 2014-04-14.
  15. ↑ Vaughan, Steven J. (2012-02-28). "New 'HTTPS Everywhere' Web browser extension released". ZDNet. Retrieved 2014-04-14.
  16. ↑ "1 SSAC Advisory on Internal Name Certificates" (PDF). ICANN Security and Stability Advisory Committee (SSAC). 15 March 2013.
  17. ↑ 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.
  18. ↑ Davis, B.; Chen, H. (2013). "Retro Skeleton". Proceeding of the 11th annual international conference on Mobile systems, applications, and services - Mobi Sys '13. p. 181. doi:10.1145/2462456.2464462. ISBN 9781450316729.
  19. ↑ Kern, M. Kathleen, and Eric Phetteplace. "Hardening the browser." Reference & User Services Quarterly 51.3 (2012): 210-214. http://eprints.rclis.org/16837/
  20. ↑ Toubiana, Vincent; Verdot, Vincent (2011). "Show Me Your Cookie And I Will Tell You Who You Are". arXiv:1108.5864Freely accessible [cs.CR].
This article is issued from Wikipedia - version of the 11/9/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.