News for hackers. Stuff that matters.
Re:Chrome 68 will mark all HTTP sites as “not secure” by judge2020 on Thursday February 08, 2018 @07:45PM (#16336953)
You can still visit websites that have an invalid CA or invalid certificate DNS match, but if the website is set up for HSTS/HSTS preload then chrome respects the website's decision to not allow insecure connections.
Re:Chrome 68 will mark all HTTP sites as “not secure” by kstrauser on Thursday February 08, 2018 @07:55PM (#16337008)
I was accessing an internal router with firmware from the distance past of 2011. Note that this is an internal-only router that connects a couple of trusted subnets, so security isn't an issue and there's no requirement to replace it yet. The problem that bit me yesterday was that I literally could not find a way to get Chrome to open https://ro.ut.er.ip/ because the router's ancient cert is invalid.

I would have been perfectly fine with Chrome alerting me to that fact and providing a "click here to continue anyway" link, but that seems to no longer be an option. FWIW, Safari did the exact same thing. Only Firefox gave me the "I promise that's really what I want to do step aside plz" button I needed.

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.
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.
Re:Chrome 68 will mark all HTTP sites as “not secure” by pavelbr on Friday February 09, 2018 @11:11AM (#16341315)
No it isn't, for certain certificate errors this is the only way.
Re:Chrome 68 will mark all HTTP sites as “not secure” by kstrauser on Friday February 09, 2018 @01:11PM (#16342468)
That freaking worked?! Thank you so much for this!
Re:Chrome 68 will mark all HTTP sites as “not secure” by Mandatum on Thursday February 08, 2018 @08:36PM (#16337205)
Yeah, it's annoying having to older versions. However there's good reason they disabled the ability via a config or launch parameter. Many organisations were not making upgrades to internal systems and websites as they could allow their browsers to bypass validation.

Still sucks for consumer grade stuff. I'm surprised your router offers SSL at all though.

Re:Chrome 68 will mark all HTTP sites as “not secure” by freehunter on Thursday February 08, 2018 @10:14PM (#16337646)
>Many organisations were not making upgrades to internal systems and websites as they could allow their browsers to bypass validation.

That's like shutting down all roads because some drivers break the speed limit. If Google isn't taking collateral damage into their decisions that impact everyone, they need to stop controlling the web.

Re:Chrome 68 will mark all HTTP sites as “not secure” by Mandatum on Thursday February 08, 2018 @10:21PM (#16337681)
The old dirt roads we used with horse and buggies are still there.
Re:Chrome 68 will mark all HTTP sites as “not secure” by nvr219 on Thursday February 08, 2018 @08:15PM (#16337104)
I had this problem with a firewall (sonicwall) and I ended up SSHing into the firewall and then allowing regular http traffic (because literally none of the browsers on my computer: ie11, firefox, or chrome would load it.)
Re:Chrome 68 will mark all HTTP sites as “not secure” by ocdtrekkie on Thursday February 08, 2018 @07:53PM (#16336996)
The problem is when Google goes and throws a commonly used internal-only TLD like .dev in their HSTS list. And of course, the whole problem that HSTS is the hosts file all over again.

That being said, the real fault in that incident is ICANN selling .dev in the first place. They should've been well aware of it's common use, and opted not to sell it.

Re:Chrome 68 will mark all HTTP sites as “not secure” by sattoshi on Thursday February 08, 2018 @09:50PM (#16337542)
I have a theory that ICANN did this too tell developers to use designated domains for internal uses.
Re:Chrome 68 will mark all HTTP sites as “not secure” by ocdtrekkie on Thursday February 08, 2018 @10:06PM (#16337604)
I think you're putting too much thought into it. It's very simple: .dev is a massively easy to monetize TLD, it was guaranteed to get multiple companies trying to buy it, and when they had multiple offers, they got auctioned.

I think .dev was just too much money for ICANN to say no.

Of course, it looks like ICANN may have gotten screwed, because Amazon and Google appear to have privately arranged to figure out who was going for which TLDs: https://icannwiki.org/.dev