Published on November 10, 2016 by Chrome
Want create site? Find Free WordPress Themes and plugins.

Emily show why the default for the web should be secure, and explain to developers the complexities and opportunities of HTTPS and HTTP/2.

Avoiding the Not Secure Warning in Chrome: goo.gl/kDg3Qu

Watch more recordings from Chrome Dev Summit ’16 at: goo.gl/TkgXYM
Subscribe to the channel: www.youtube.com/chromedevelopers
Music by Terra Monk: goo.gl/xolmTV

Did you find apk for android? You can find new Free Android Games and apps.

Leave a Reply

5 Comments on "Security (HTTP/2 leading to HTTPS) (Chrome Dev Summit 2016)"

Notify of
avatar

3m0_Wr3ck
Guest
3m0_Wr3ck
11 months 3 days ago

why not provide easy to use and or free ssl certs for web devs?

3m0_Wr3ck
Guest
3m0_Wr3ck
11 months 1 day ago

+Ronald Tetsuo Miura I'm considering along the lines of a host, firm, organization, manufacture ISO ( and or where applicable ).

Ronald Tetsuo Miura
Guest
Ronald Tetsuo Miura
11 months 1 day ago

Fair point. Having the keys to the kingdom stored in a single place is probably not a good idea :). Hopefully, other cert providers will follow suit and make their tools better.

3m0_Wr3ck
Guest
3m0_Wr3ck
11 months 1 day ago

+Ronald Tetsuo Miura I know of this service but think it's potentially dangerous to have a single point of open access to certs for the entire internets. I'm trying to drive the point for industry wide standardization of easy straight forward cert provisioning.

Ronald Tetsuo Miura
Guest
Ronald Tetsuo Miura
11 months 1 day ago

Something letsencrypt.org/ doesn't already provide?

wpDiscuz