project_path: /web/_project.yaml book_path: /web/shows/_book.yaml description: Making Chrome secure.

{# wf_updated_on: 2018-07-17 #} {# wf_published_on: 2018-07-17 #} {# wf_podcast_audio: https://storage.googleapis.com/http-203-podcast/io-2018-emily-chris.mp3 #} {# wf_podcast_duration: 00:14:40 #} {# wf_podcast_fileSize: 10935407 #} {# wf_podcast_subtitle: Making Chrome secure. #} {# wf_featured_image: /web/shows/http203/podcast/images/io.jpg #} {# wf_blink_components: Blink>SecurityFeature #}

I/O chat with Emily Schechter and Chris Palmer {: .page-title }

In this episode we chat to Emily Schechter and Chris Palmer, who work on the security team for Chrome. We cover stuff like:

What Meltdown and Spectre are, and why they're a problem.
How annoying it is when someone conducts a sound test while you're trying to record a podcast.
Cross-origin read blocking.
Samesite cookies.
Getting the long tail of the web onto HTTPS.
Updating Chrome's UI to indicate HTTP is "not secure".

Also check out Emily and Chris's I/O talk, Palmer and Schechter on Meltdown and Spectre.

<a href="http://feeds.feedburner.com/Http203Podcast"> <span class="material-icons">rss_feed</span> Subscribe </a>