Chrome will mark all HTTP sites as ‘not secure’ starting in July • Hacker News Board

Re: Chrome will mark all HTTP sites as ‘not secure’ starting in July

#141

Post by icedchai » Thu, Jul 12, 2018, 3:46 PM UTC

sarif wrote: post #139

icedchai wrote: post #138

Earlier quoted context omitted.

It's easy for people like us to set it up. I've set up Letsencrypt many, many times. Now, imagine you are Joe Blow hosting his blog on some small web host that barely supports Wordpress. Logging into CPanel is confusing to you. How do you deploy SSL?

that is a fair point.

It looks like CPanel does support a letsencrypt plugin, which is really cool: https://blog.cpanel.com/announcing-cpanel-whms-official-lets...

However, I have to wonder how many hosts actually enable it...

Re: Chrome will mark all HTTP sites as ‘not secure’ starting in July

#142

Post by jacksmith21006 » Thu, Jul 12, 2018, 6:17 PM UTC

Good to see Google doing this. Really no execuse any longer to have not implemenated TLS/SSL.

Re: Chrome will mark all HTTP sites as ‘not secure’ starting in July

#143

Post by AFNobody » Fri, Jul 13, 2018, 1:32 AM UTC

AgentME wrote: post #117

AFNobody wrote: post #110

Earlier quoted context omitted.

If a hostile controls a DNS server, you are hosed anyway.

If the sites you care about are using HSTS (and they're in the HSTS preload list, or you've visited them before from this device), then the worst the attacker can do is deny you from accessing them.

HSTS depends on DNS and NTP.