{"id":3061,"date":"2016-09-23T13:41:44","date_gmt":"2016-09-23T13:41:44","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=3061"},"modified":"2016-09-23T13:43:47","modified_gmt":"2016-09-23T13:43:47","slug":"cloudflare-debuts-improvements","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/cloudflare-debuts-improvements\/","title":{"rendered":"Cloudflare Debuts Improvements During \u201cEncryption Week\u201d"},"content":{"rendered":"<h2>TLS 1.3, Opportunistic Encryption, and Automatic HTTPS Rewrites.<\/h2>\n<p>Cloudflare has deemed this to be \u201c<a href=\"https:\/\/blog.cloudflare.com\/encryption-week\/\" rel=\"nofollow\">Encryption Week<\/a>\u201d and will be rolling out three major improvements to their network\u2019s SSL\/TLS capabilities.<\/p>\n<p>The improvements are designed to improve performance, ease deployment of SSL, and make encrypted connections available to a wider audience.<\/p>\n<p>All of these new features are now available to all Cloudflare customers, including their free plan users.<\/p>\n<h2>TLS 1.3<\/h2>\n<p>The newest version of our favorite protocol \u2013 TLS 1.3 \u2013 is still being drafted by the <a href=\"https:\/\/www.ietf.org\/\">IETF<\/a>. But that is not stopping Cloudflare from deploying the in-progress protocol.<\/p>\n<p>With new authenticated encryption suites that improve security, and major improvements in performance \u2013 TLS 1.3 handshakes can <a href=\"https:\/\/blog.cloudflare.com\/introducing-tls-1-3\/#improvedspeed\" rel=\"nofollow\">be up to 40% faster<\/a> \u2013 it\u2019s no wonder why they are eager to start as soon as possible.<\/p>\n<figure id=\"attachment_3062\" aria-describedby=\"caption-attachment-3062\" style=\"width: 975px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3062\" src=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2016\/09\/CloudFlare.png\" alt=\"Cloudflare\" width=\"975\" height=\"524\" srcset=\"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2016\/09\/CloudFlare.png 975w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2016\/09\/CloudFlare-300x161.png 300w, https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2016\/09\/CloudFlare-768x413.png 768w\" sizes=\"auto, (max-width: 975px) 100vw, 975px\" \/><figcaption id=\"caption-attachment-3062\" class=\"wp-caption-text\">The TLS 1.3 Handshake can be completed with fewer \u201croundtrip\u201d connections, which can significantly reduce connection time. Image courtesy of Cloudflare.<\/figcaption><\/figure>\n<p>The TLS 1.3 Handshake can be completed with fewer \u201croundtrip\u201d connections, which can significantly reduce connection time. Image courtesy of Cloudflare.<\/p>\n<p>If you are a Cloudflare user, <a href=\"https:\/\/blog.cloudflare.com\/introducing-tls-1-3\/#liveforall\" rel=\"nofollow\">you need to opt in to TLS 1.3<\/a>. On the client side, you won\u2019t see any changes unless you are using developer releases of Chrome or Firefox; since TLS 1.3 is still being drafted the standard versions of browsers don\u2019t yet support it.<\/p>\n<h2>Automatic HTTPS Rewrites<\/h2>\n<p>One of the biggest problems websites face when adopting HTTPS is mixed content.<\/p>\n<p>Mixed content is when a given page has both HTTP and HTTPS resources. When this happens browsers treat the page as insecure because all the resources can\u2019t be loaded safely. That means no green padlock or EV address bar \u2013 and that your users aren\u2019t entirely protected.<\/p>\n<p>Fixing mixed content isn\u2019t always easy \u2013 <a href=\"https:\/\/www.thesslstore.com\/blog\/wired-com-yelp-com-transition-https\/\">even major sites struggle with it<\/a> \u2013 because there are a variety of reasons why it exists in the first place. When HTTPS simply isn\u2019t supported by a site, there is not going to be an easy solution.<\/p>\n<p>But one of the most common sources of mixed content does have an easy fix. Many sites that do have HTTPS capabilities simply aren\u2019t taking full advantage \u2013 usually because their source code has explicitly written HTTP links, causing browsers to load the content insecurely. In this case \u201cmanually changing \u201chttp\u201d to \u201chttps\u201d in the page\u2019s source is often enough to fix mixed content.\u201d<\/p>\n<p>But administrators may not know that this needs to be done, and \u201cmany sites can\u2019t do that because their sites are created dynamically by content management systems or they include third party resources that they have no control over.\u201d<\/p>\n<p>That\u2019s why Cloudflare is introducing <a href=\"https:\/\/blog.cloudflare.com\/encryption-week\/#automatichttpsrewritesfixingmixedcontentautomatically\" rel=\"nofollow\"><em>Automatic HTTPS Rewrites<\/em><\/a>. They will simply spot mixed content and upgrade URLs from \u201cHTTP\u201d to \u201cHTTPS.\u201d<\/p>\n<p>Cloudflare will detect when this can be done by looking at \u201cEFF\u2019s HTTPS Everywhere list, Chrome\u2019s HSTS preload list\u201d to know what sites can support HTTPS without introducing any breakage. Over time, Cloudflare hopes to build their own list to expand compatibility.<\/p>\n<h2>Opportunistic Encryption<\/h2>\n<p>Opportunistic Encryption (OE) is an alternative to traditional HTTPS. Instead of <em>real <\/em>\u201cHTTPS\u201d that we know and love, it\u2019s \u201cHTTP requests with Opportunistic Encryption over TLS.\u201d<\/p>\n<p>The difference is subtle, but important. Opportunistic Encryption allows HTTP requests to be made over an encrypted TLS connection. OE can even be used with a valid and trusted certificate.<\/p>\n<p>It may help to think of Opportunistic Encryption as <em>Optional Encryption. <\/em>It tells the browser to use encryption <em>if it can<\/em>. If it can\u2019t, that\u2019s okay. This means there are no security guarantees.<\/p>\n<p>Therefore, browsers treat OE differently. Sites using OE are still accessed over HTTP. \u201cUsers will not see a security indicator\u2026 in the address bar when visiting a site using Opportunistic Encryption, but the connection from the browser to the server is encrypted.\u201d<\/p>\n<p>Nick Sullivan, Cloudflare\u2019s Cryptography lead, wrote \u201cto be clear, Opportunistic Encryption is not a replacement for HTTPS.\u201d<\/p>\n<p>Despite the drawbacks, OE is helpful for sites that can\u2019t adopt HTTPS yet \u2013 primarily websites that have unfixable mixed content issues.<\/p>\n<p>Because OE connections are encrypted, it will allow those sites to use HTTP\/2. Though, only with browsers that support OE. Currently, that would only be Firefox (after all, the technology was designed by Mozilla engineers).<\/p>\n<p>For now, Opportunistic Encryption is essentially some clever engineering to spread transport encryption to a small section of the internet. If you want to learn more about OE, <a href=\"https:\/\/blog.cloudflare.com\/opportunistic-encryption-bringing-http-2-to-the-unencrypted-web\/\" rel=\"nofollow\">Cloudflare has an entire blog post<\/a> on the topic.<\/p>\n<h2>Encryption for All!<\/h2>\n<p>Cloudflare has been <a href=\"https:\/\/blog.cloudflare.com\/ssl-week-means-less-weak-ssl\/\" rel=\"nofollow\">doing a lot<\/a> to make it easier for websites to deploy HTTPS and HTTP\/2. As one of the world\u2019s largest CDNs, these latest improvements are giving new technologies a huge jump start in adoption.<\/p>\n<p>TLS 1.3 isn\u2019t even finalized yet and already more than <a href=\"https:\/\/twitter.com\/grittygrease\/status\/778221231505969152\" rel=\"nofollow\">4 million sites<\/a> support it thanks to Cloudflare! We can\u2019t wait to see what they rollout next.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TLS 1.3, Opportunistic Encryption, and Automatic HTTPS Rewrites. Cloudflare has deemed this to be \u201cEncryption Week\u201d and will be rolling out three major improvements to their network\u2019s SSL\/TLS capabilities. The&#8230;<\/p>\n","protected":false},"author":2,"featured_media":3063,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":"","tve_updated_post":"","tve_custom_css":"","tve_user_custom_css":"","tve_globals":{},"tcb2_ready":0,"tcb_editor_enabled":0,"tve_landing_page":"","_tve_header":"","_tve_footer":""},"categories":[130],"tags":[213,217,215,136,214],"class_list":["post-3061","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-everything-encryption","tag-cloudflare","tag-encryption-week","tag-opportunistic-encryption","tag-ssl","tag-tls-1-3","post-with-tags"],"views":5965,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2016\/09\/Depositphotos_61156269_m-2015.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/3061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/comments?post=3061"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/3061\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/3063"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=3061"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=3061"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=3061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}