News for hackers. Stuff that matters.
Re:Towards HTTPS by Default by Volundr on Wednesday August 16, 2023 @06:20PM (#37154654)
My home router for example always throws up a big scary https warning. I'd also very much prefer it if more smart devices were local network only rather than relying on a vendors website being up in perpetuity.

I'm actually not against browsers pushing HTTPS, I'm all for it. But it is a fair criticism that there are real downsides that there currently isn't a good user friendly solution for.

Re:Towards HTTPS by Default by aaomidi on Wednesday August 16, 2023 @08:47PM (#37155780)
Use Caddy as your webserver, use the DNS01 challenge, and you're done?

Don't expose your local stuff over the internet without encryption. The ISP doesn't need to see that.

Re:Towards HTTPS by Default by kalleboo on Thursday August 17, 2023 @03:31AM (#37158380)
How is your home internet router going to retrieve a certificate from Let's Encrypt before you have logged in and configured it to connect to the internet?
Re:Towards HTTPS by Default by aaomidi on Thursday August 17, 2023 @03:31PM (#37166765)
Your preloaded root chain? I mean you can also trust on first use if you really want to.
Re:Towards HTTPS by Default by kalleboo on Friday August 18, 2023 @04:44AM (#37172885)
My point is this.

I'm a consumer. I buy a new router. I need to log into its web interface to enter the PPPoE credentials from my ISP before it can go online. I plug it in, and browse to 192.168.0.1. Chrome says in big letters "PAGE IS NOT SECURE YOU ARE BEING HACKED DON'T VISIT THIS PAGE".

This situation means the router can't go online to generate a trusted certificate, and it's left with either HTTP or a self-signed certificate, both of which Chrome will present as inherently dangerous.

The solution that router manufacturers seem to be going with are "you must own an Apple or Google OS device, pray that we still have our app on the store in your country and support your router, and accept our onerous privacy terms"

> you can also trust on first use if you really want to

That's a totally acceptable solution! But one that Chrome does not seem interested in making look safe to users. They could do it for known-local IP ranges and hit 99% of the use cases (10., 192.168. etc)

Re:Towards HTTPS by Default by janosdebugs on Friday August 18, 2023 @06:21AM (#37173648)
Curious: is this how routers are handled where you live? In Austria and the neighboring countries you typically get a device from the provider preconfigured, even if you don't want one.
Re:Towards HTTPS by Default by kalleboo on Friday August 18, 2023 @07:18AM (#37174144)
Yeah. You're only guaranteed to get a free router if you also sign up for VoIP service which requires it and even then it will probably be wired-only and need a card to upgrade it to WiFi.
Re:Towards HTTPS by Default by janosdebugs on Saturday August 19, 2023 @10:05AM (#37188904)
Ohwow, that's less than ideal. I wish I could convince my provider to let me use my own router so I can get rid of the double NAT, but I'm probably 1 in 10000.
Re:Towards HTTPS by Default by aaomidi on Saturday August 19, 2023 @04:47PM (#37193019)
“ This situation means the router can't go online to generate a trusted certificate, and it's left with either HTTP or a self-signed certificate, both of which Chrome will present as inherently dangerous.”

What are you on about? How does the router not having a valid certificate mean it “can’t go online”?

Re:Towards HTTPS by Default by janosdebugs on Wednesday August 16, 2023 @11:35PM (#37156852)
These days most non-IT people I know log in to their wifi network with the credentials printed on the sticker on the bottom. They wouldn't touch the web interface if their life depended on it.
Re:Towards HTTPS by Default by chii on Thursday August 17, 2023 @03:59AM (#37158556)
which just exposes the wifi as an unsecured network, leading to far worse outcomes!
Re:Towards HTTPS by Default by janosdebugs on Thursday August 17, 2023 @05:21AM (#37159176)
Which is why having secure connections enforced for the typical use case is doubly important. We can't wish a more secure solution into existence, this is how internet providers handle it in a great many places. Make TLS enforcement a very well hidden setting to turn it off/bypass, but don't let the average user anywhere near this.