5 ms·
So has Google said how they expect router configuration pages, network printers, NAS boxes and other local-network-connected devices to deal with this? I mean,
by michaelt 8y ago
So has Google said how they expect router configuration pages, network printers, NAS boxes and other local-network-connected devices to deal with this?
I mean, I know Plex has an arrangement where they provide a dynamic DNS style record and they have a special deal with Digicert to issue loads of wildcard certificates [1] but that needs a bunch of infrastructure and a special deal with a CA, as well as precluding offline use and breaking if the supplier ever drops support.
And obviously, you can also use a self-signed certificate - but that means teaching users "Just click ignore on the invalid certificate warning" and I've heard people say we shouldn't train users to ignore invalid certificate warnings.
Is there some alternative solution Google is proposing?
[1] https://blog.filippo.io/how-plex-is-doing-https-for-all-its-users/ https://blog.filippo.io/how-plex-is-doing-https-for-all-its-...
- robin_reala 8y agoWhat’s to deal with? It’s still the same as before: not secure.
- y0ghur7_xxx 8y ago> What’s to deal with? It’s still the same as before: not secure. But there is no meaningful way to make it secure. So marking it not secure creates just noise.
- dullgiulio 8y agoWell, also the "delayed" notice at the gate of an airport makes noise. It's informative: you might not be able to do anything about it, but you should know it anyway.
- y0ghur7_xxx 8y agoThere is a difference between an information and a warning. If I am entering information on an unencrypted connection on the internet I want a warning. And I don't want to get accustomed to that warning, because if it happens I want to be alerted. If the same thing happens in my local lan I don't want the same warning, because if I get the same warning I will start to ignore it, and not only when I'm in my local lan.
- fulafel 8y agoYour devices can get letsencrypt certs just like before. Or users get notified about how the connection is in plaintext. Both are improvements to the previous situation.
- y0ghur7_xxx 8y ago> Your devices can get letsencrypt certs I don't want all my internal network hosts exposed on a certificate transparency log. I want my http connections to work without scary warnings in my local home network. Because if you show me scary warnings, and no meaningful way to implement the http connection securely, I will just start to ignore them. And if I ignore them in my lan, I will ignore them on the internet too. And that would be a net security loss. So either use something else entirely inside a lan, like ToFU like ssh, or allow http connections without tls and without scary warnings. But I think deprecating http in local home lans with no meaningful way to make them secure is not a step in the right direction.
- notzuck 8y agoYou're right but nobody cares - the market share of people with your problem is small and software vendors like Google will probably not spend too much money catering for people like you. Harsh but true.
- y0ghur7_xxx 8y ago> the market share of people with your problem is small I don't have stats or data, but I don't think the households with devices that have web interfaces like a nas, routers, media centers, and stuff like this are small.
- notzuck 8y agoYes it is and if you look at something like routers, most people will never look at the web interface (or know it exists). You are overestimating the general publics technical savvy and accessing a web interface counts as technical savvy.
- exikyut 8y agoWell, Chrome whitelists localhost for all the new features (like subtleCrypto) that don't work on non-HTTPS. But expanding that to the local LAN will promptly fall over as soon as captive proxies (which make remote sites look like they're in the local LAN) get involved.