Download as PDF, PPTX
Uploaded byPaul Schreiber
WordCamp US: Delivering the news over HTTPS
The Chrome security team plans to phase out non-secure HTTP to enhance user security and privacy by marking it as non-secure and eventually restricting new features to secure websites only. They encourage all website operators to transition to HTTPS by the end of 2015. This initiative aims to ensure that all browsing activities are treated as private and sensitive.
More Related Content
Similar to WordCamp US: Delivering the news over HTTPS
WordCamp US: Delivering the news over HTTPS
- 1.
- 2.
- 7.
- 8.
- 10. Marking HTTP AsNon-Secure We, the Chrome Security Team, propose that user agents (UAs) gradually change their UX to display non-secure origins as affirmatively non-secure. We intend to devise and begin deploying a transition plan for Chrome in 2015. The goal of this proposal is to more clearly display to users that HTTP provides no data security.
- 11. Marking HTTP AsNon-Secure We, the Chrome Security Team, propose that user agents (UAs) gradually change their UX to display non-secure origins as affirmatively non-secure. We intend to devise and begin deploying a transition plan for Chrome in 2015. The goal of this proposal is to more clearly display to users that HTTP provides no data security.
- 13. Deprecating Non-Secure HTTP Todaywe are announcing our intent to phase out non-secure HTTP. There are two broad elements of this plan: 1. Setting a date after which all new features will be available only to secure websites 2. Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.
- 14. Deprecating Non-Secure HTTP Todaywe are announcing our intent to phase out non-secure HTTP. There are two broad elements of this plan: 1. Setting a date after which all new features will be available only to secure websites 2. Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.
- 15. Deprecating Non-Secure HTTP Todaywe are announcing our intent to phase out non-secure HTTP. There are two broad elements of this plan: 1. Setting a date after which all new features will be available only to secure websites 2. Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.
- 17. The HTTPS-Only Standard Allbrowsing activity should be considered private and sensitive. —https.cio.gov
- 19. A Call toAction If you run a news site, or any site at all, we’d like to issue a friendly challenge to you. Make a commitment to have your site fully on HTTPS by the end of 2015 and pledge your support with the hashtag #https2015. —Eitan Konigsburg, Rajiv Pant and Elena Kvochko “Embracing HTTPS” November 13, 2014
- 23.
- 24.
- 28.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 53. Selected DV Certificates ComodoPositiveSSL Comodo SSL Thawte SSL123 0 32 64 96 128 160 149 99 49
- 54. PositiveSSL DV Certificates SSLs.com SSLMate Comodo 032 64 96 128 160 49 15.95 8.95
- 55. Selected Certificates Let’s Encrypt PositiveSSL(SSLs.com) GeoTrust QuickSSL Premium Thawte SSL123 GeoTrust True BusinessID Symantec Secure Site Symantec Secure Site Pro EV 0 300 600 900 1200 1500 1400 399 199 149 99.98 8.95 0
- 58.
- 59.
- 60.
- 61.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 89. 2008 HTTPS isslow
- 90. 2008 HTTPS isslow 2015 HTTPS is fast
- 91.
- 92.
- 93.
- 95.
- 96.
- 97.
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105. Many graphics fromThe Noun Project Tombstone by Jakob Wells. Congress by Martha Ormiston. Shield by Wayne Thayer. Snail by aLf. Server by Yazmin Alanis. SEO by Azis. Money by Nick Levesque. Warning by Icomatic. Shopping cart by Patrizia Daidone. Lock with keyhole by Brennan Novak. Scribble by Michael Chanover. Calendar by Mani Amini. Error by Anas Ramadan. Network by Stephen Boak. Hat based on work by Blake Kimmel.