Hacker News Reader

Comment by kstrauser | Hacker News Reader

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.

View on HN

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.

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...

It's just a shortcut to avoid clicking on two buttons.

No it isn't, for certain certificate errors this is the only way.

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.

That freaking worked?! Thank you so much for this!

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.

>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.

The old dirt roads we used with horse and buggies are still there.

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.)

Reply on news.ycombinator.com