Chrome 68 will mark all HTTP sites as “not secure”

Re:Chrome 68 will mark all HTTP sites as “not secure” by gsich on Friday February 09, 2018 @09:19AM (#16340305)

Then you usually don't need a certificate from a CA. Just selfsign.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by fps on Friday February 09, 2018 @11:40AM (#16341623)

This seems like it's going in circles, but, if you selfsign modern browsers display a big scary warning. If you're making a device or software meant to live behind a firewall and to be accessed from a browser, users will either have to install your CA in their browsers, or deal with the big scary warning. Both of which are bad.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by gsich on Friday February 09, 2018 @11:43AM (#16341647)

If you don't have a domain, chances are that you don't provide service to normal users. Or to users at all besides yourself.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by pessimizer on Friday February 09, 2018 @01:15PM (#16342503)

> chances are that you don't provide service to normal users. Or to users at all besides yourself.

I think that's the point. Creating friction that scares normie users when people are using web UIs on local networks puts non-cloud based products at a disadvantage against the centralized giants.

[ Parent | on HN ]