 Hey everybody, what's up? It's Rob Dodson. Welcome back to the Chrome Dev Summit. We are here at the SF Jazz Center I'm joined by Emily Stark. Emily, you just gave a presentation on HTTPS on the web and some of the changes that are coming to Chrome around that So for folks who haven't caught the talk yet Can you just tell them a little bit about some of the new things that are coming in in Chrome for security in HTTPS? Sure. So in Chrome 56, which is going to stable in January We're launching a new UI treatment for insecure HTTP pages And this is specifically for insecure HTTP pages that have passwords or credit card fields for those pages what we're going to do is show in the omnibox a label that says not secure and our hope is that Users will learn from this that they're in a particularly sensitive situation where they're including where they're sending their passwords or credit cards And we want them to know that they're not doing that over a secure connection So You know why not just go full-blown like scary warning and be like yo, this is like an evil website or whatever Why not why not take a maybe a stricter or stronger approach when doing this kind of thing? So we definitely want to do that eventually eventually. We plan to show a very prominent Real warning about the risks of HTTP But we still need developers help to adopt HTTPS. We're not all the way there yet We don't have HTTPS everywhere and in fact, there are quite a few sites still using insecure HTTP So we think that if we were to just turn on this really scary aggressive warning right away tomorrow We would end up scaring some users confusing them or they might just learn to tune it out And all of those are bad outcomes for us Okay, and so and that makes a lot of sense I'm personally not a security expert I'm imagining there's there's a few folks out there watching who are also not security experts So for developers who know this this is important, but aren't quite sure like where to get started Like what are what are some resources that they could check out? So one resource that we like to recommend is the dev tools security panel So if you move your site to HTTPS and then you open up Chrome's developer tools You can look there's a security tab there that is designed to help developers figure out if they've done it right Find and fix any problems with their HTTPS configuration So that's a great resource for developers who are into turning on HTTPS But not necessarily experts and we also have some documentation on the web We have a web fundamentals guide. So if you search for web fundamentals for HTTPS There is a whole bunch of information in there about Configuring HTTPS performance tuning search ranking all all the hurdles that you might run into when setting up HTTPS Okay, right on this sound like awesome resources. So definitely go check those out Emily. Thank you so much for being with us today Thank you all so much for watching again We're coming at you live from the SFJAS Center Chrome Dev Summit stay with us We've got a bunch more content that's going up on our channel We've also got an entire second day of content that'll be happening Live from this floor tomorrow. So be sure to tune in on the live stream for that as well again I'm Rob Dodson Emily again. Thank you so much. Thank you for watching stay with us