Re:Chrome 68 will mark all HTTP sites as “not secure”
by epmatsw on Thursday February 08, 2018 @10:19PM
(#16337672)
Pro-tip: On Chrome's certificate error page, you can type "badidea" (or "thisisunsafe" in 66 or later) to force it to let you through.
[ Parent
| on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure”
by toyg on Friday February 09, 2018 @02:37AM
(#16338573)
I hope you’re joking...? An interface that forbids you from working unless you know an easter-egg/“insider” password is almost a fascist concept. I guess that’s another reason not to use Chrome...
Re:Chrome 68 will mark all HTTP sites as “not secure”
by epmatsw on Friday February 09, 2018 @09:58AM
(#16340582)
For HSTS, it’s based on the spec. There’s not supposed to be a user-accessible override for HSTS errors, which is why Chrome hides it behind that easter egg. Firefox has no override of any kind.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by jrimbault on Friday February 09, 2018 @04:28AM
(#16338980)
It's just a shortcut to avoid clicking on two buttons.