{"id":4194,"date":"2017-06-06T09:55:51","date_gmt":"2017-06-06T13:55:51","guid":{"rendered":"https:\/\/www.thesslstore.com\/blog\/?p=4194"},"modified":"2017-06-07T03:48:05","modified_gmt":"2017-06-07T07:48:05","slug":"security-changes-in-chrome-59","status":"publish","type":"post","link":"https:\/\/www.thesslstore.com\/blog\/security-changes-in-chrome-59\/","title":{"rendered":"Browser Watch: SSL and Security Changes in Chrome 59"},"content":{"rendered":"<h2>Security Changes in Chrome 59: worker-src support, rate limits on permission requests and headless chrome&#8230;<\/h2>\n<p>It\u2019s time to talk security changes in Chrome 59. In this release, Google went pretty light on changes directly related to SSL\/TLS, so we have included other changes that developers who work with SSL and HTTPS may be interested in.<span id=\"newline\"><\/span><\/p>\n<p>The biggest on-going event in the industry is <a href=\"https:\/\/www.thesslstore.com\/blog\/google-and-symantec\/\">Symantec\u2019s mis-issuance troubles<\/a>. Google, Mozilla, and other root programs are still deciding how to handle these issues. The proposals put forth by Google and Mozilla would require Symantec to partner with a third-party CA to handle certificate issuance while it improves its own operations and get new roots trusted.<\/p>\n<p>Because Google is still working on finalizing its plans, there are no changes related to the trust of Symantec certificates in this release.<\/p>\n<p>In addition to the changes listed below, three <a href=\"https:\/\/chromereleases.googleblog.com\/2017\/06\/stable-channel-update-for-desktop.html\" rel=\"nofollow\">URL spoofing bugs were also fixed<\/a> (one with \u201chigh\u201d severity). Chrome\u2019s policy is to withhold the details of those bugs for 14 weeks so that the majority of users can safely update their browsers.<\/p>\n<p>Here are some of the biggest security changes in Chrome 59:<\/p>\n<h2><a href=\"https:\/\/bugs.chromium.org\/p\/chromium\/issues\/detail?id=688510\" rel=\"nofollow\">Venafi Gen2 CT Log\u00a0 Added<\/a>:<\/h2>\n<p>Venafi\u2019s Gen2 log is now trusted by Chrome. It accepts certificates from all roots trusted by Chrome. Earlier this year, Venafi had a <a href=\"https:\/\/groups.google.com\/a\/chromium.org\/d\/msg\/ct-policy\/KMAcNT3asTQ\/UgJ70hvBBQAJ\" rel=\"nofollow\">log removed from Chrome<\/a> after suffering stability problems.<\/p>\n<p>&nbsp;<\/p>\n<h2><a href=\"https:\/\/www.chromestatus.com\/feature\/5922594955984896\" rel=\"nofollow\">Support Added for worker-src<\/a><\/h2>\n<p>Worker-src is a directive for Content Security Policy (CSP) Level 3. It allows websites to restrict acceptable URLs\/origins for Workers, SharedWorker, and ServiceWorker.<\/p>\n<p>Worker-src <a href=\"https:\/\/w3c.github.io\/webappsec-csp\/#directive-worker-src\" rel=\"nofollow\">is defined here in the CSP Level 3 spec<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h2><a href=\"https:\/\/www.chromestatus.com\/feature\/5709390967472128\" rel=\"nofollow\">Support Dropped for FTP Subresources<\/a><\/h2>\n<p>Pages loading over HTTP\/HTTPS will no longer be allowed to load resources from the ftp:\/\/ protocol.\u00a0 An example of this would be the URL \u201chttp:\/\/example.com\/index.html\u201d attempting to load \u201cftp:\/\/example.com\/image.jpeg.\u201d<\/p>\n<p>Chrome 59 is totally blocking this behavior, and ultimately wants <a href=\"https:\/\/github.com\/whatwg\/fetch\/pull\/464#issuecomment-278275276\" rel=\"nofollow\">to remove native FTP support altogether<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<h2><a href=\"https:\/\/www.chromestatus.com\/feature\/6443143280984064\" rel=\"nofollow\">Temporary Rate Limit on Permission Requests<\/a>:<\/h2>\n<p>To stop websites from spamming permission requests, Chrome will now temporarily stop all requests after the third dismissal of a prompt. After the 3<sup>rd<\/sup> dismissal, future requests will be stopped for a week. Each further dismissal will re-activate the 1-week \u2018cooldown.\u2019<\/p>\n<p>&nbsp;<\/p>\n<h2><a href=\"https:\/\/developers.google.com\/web\/updates\/2017\/04\/devtools-release-notes#block-requests\" rel=\"nofollow\">Block Specific Network Requests in Dev Tools<\/a><\/h2>\n<p>A new feature in Chrome\u2019s Developer Tools allows you to block resources based on its request URL or file type. This is helpful for testing how a site performs when a specific resource is blocked and can be used to simulate certain origins being offline. You can use wildcard functionality to block entire file types, such as \u201c*.css.\u201d<\/p>\n<p>Google\u2019s regular <a href=\"https:\/\/developers.google.com\/web\/updates\/2017\/04\/devtools-release-notes#block-requests\" rel=\"nofollow\"><em>What\u2019s New in DevTools <\/em>update has more<\/a> on this feature.<\/p>\n<p>&nbsp;<\/p>\n<h2><a href=\"https:\/\/developers.google.com\/web\/updates\/2017\/04\/headless-chrome\" rel=\"nofollow\">Headless Chrome has Shipped<\/a><\/h2>\n<p>A \u201cheadless environment\u201d is an interface that lacks a GUI and is instead console based. A headless browser is all the components of a browser without the GUI. It is designed for development, automated testing, and other automated tasks that don\u2019t require user interaction via a GUI.<\/p>\n<p>For example, you could use a headless browser to automatically connect to a URL at set intervals and take screenshots of the page for archiving or monitoring.<\/p>\n<p>Headless Chrome is available for Linux and Mac in Chrome 59. Windows compatibility will be coming later.<\/p>\n<p>To learn more about headless Chrome, <a href=\"https:\/\/developers.google.com\/web\/updates\/2017\/04\/headless-chrome\" rel=\"nofollow\">check out this article from Google<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Security Changes in Chrome 59: worker-src support, rate limits on permission requests and headless chrome&#8230; It\u2019s time to talk security changes in Chrome 59. In this release, Google went pretty&#8230;<\/p>\n","protected":false},"author":2,"featured_media":4198,"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":[17],"tags":[243,131,155,279],"class_list":["post-4194","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry-lowdown","tag-browser-watch","tag-google","tag-google-chrome","tag-web-browsers","post-with-tags"],"views":15635,"jetpack_featured_media_url":"https:\/\/www.thesslstore.com\/blog\/wp-content\/uploads\/2017\/06\/iStock-458077943.jpg","_links":{"self":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/4194","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=4194"}],"version-history":[{"count":0,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/posts\/4194\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media\/4198"}],"wp:attachment":[{"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/media?parent=4194"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/categories?post=4194"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thesslstore.com\/blog\/wp-json\/wp\/v2\/tags?post=4194"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}