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

Re:Chrome 68 will mark all HTTP sites as “not secure” by tomphoolery on Friday February 09, 2018 @04:44PM (#16344098)

Your problem is isolated to local development servers, which can be easily excepted from blocking non-HTTPS sites. The potential privacy/security gains totally outweigh the inconvenience of seeing "Not Secure" in the URL bar of your browser on an app you are developing.

This isn't as big of a problem as you'd like to believe. IMHO.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by aurelian15 on Saturday February 10, 2018 @12:32AM (#16346046)

Sorry for not being clear enough in my initial post. I'm not talking about a development server. I'm talking about the end product being a server. For example in the form of a user-friendly executable that is natively running on your Windows/Linux/macOS Desktop, a Mobile device, or (alternatively) a single-board computer such as a Raspberry Pi. The end-users using this are not developers. They are just normal users running a simple piece of software that provides them with a web-frontend for a service in their home-network. No internet connection required whatsoever.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by kuschku on Friday February 09, 2018 @05:25PM (#16344398)

So, how do I build an IoT device that never sends a single packet outside of my LAN, which my grandma could have set up and run without ever seeing a security warning, and which does not show "Not Secure"?

In general, how can I get all the functionality e.g. a Nest device may provide, while staying purely within of my LAN?

(Disclaimer: For my own IoT projects, of course I use a special domain with DNS delegation and Let's Encrypt certificates, and HSTS preloaded)

[ Parent | on HN ]