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

Re:Chrome 68 will mark all HTTP sites as “not secure” by orangecat on Thursday February 08, 2018 @11:29PM (#16337890)

There are plenty of instances where websites do not need to use HTTPS

No there aren't.

like simple static websites for small businesses that do not collect personal user information

Until the connection gets MITMed to return a fake login page.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by throwaway2048 on Friday February 09, 2018 @12:35AM (#16338125)

Please tell me a way to enable https for local LAN only devices that does not involve me MITM'ing every connection to them..

[ Parent | on HN ]

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

This centralizes publishing rights to browser vendors & security cert vendors. I don't want to take permission from any third-party before publishing content on the web.

In any case, its rather rude of you to presume to know what people should think about this topic.

[ Parent | on HN ]

Re:Chrome 68 will mark all HTTP sites as “not secure” by gmueckl on Friday February 09, 2018 @12:34AM (#16338117)

What login page? Your typical company website just has a few pages of text without any active elements. Forcing those to buy SSL certificates creates just another artificial barrier to entry.

[ Parent | on HN ]

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

Whatever login page the attacker wants to present. They're betting percentages.

Google. Amazon. sac.mil. fed.gov. Whatevs.

[ Parent | on HN ]