4 ms·
I'm not sure that this is a real issue. Self-signed certificates can be accepted under a TOFU (trust on first use) pattern; the user only has to click through
by zozbot234 6y ago
I'm not sure that this is a real issue. Self-signed certificates can be accepted under a TOFU (trust on first use) pattern; the user only has to click through a scary browser warning once, and then "save" the exception locally on her machine.
- tsimionescu 6y agoThat only works on Firefox. For all other browsers, you need to go through an extremely cumbersome process to install the certificates in the Windows trust store. This is not even possible on my work-issued laptop for example. It's really annoying that the only way to provide secure HTTPS is to make your local devices dependent on a public service and abuse DNS resolution. Hopefully as more and more people encounter this problem, some router-based certificate signing protocol will become known and accepted, maybe even with some kind of extension to DHCP to allow advertising the root cert of the router. Of course, a lot of care would need to be taken to make it hard to accidentally trust some cafe wi-fi...
- Wowfunhappy 6y ago(On Mac, it works in Safari too—it'll actually add the certificate to macOS's Keychain.)
- zozbot234 6y ago> That only works on Firefox. For all other browsers, you need to go through an extremely cumbersome process to install the certificates in the Windows trust store. This is a bug in those browsers, then. It's totally fine to use the system certificate store as a default, but it should be possible to trust other certificates at a more localized level - perhaps for a limited time, but not in a way that's limited to a single browser session.
- rektide 6y agoChrome is building their own root certificate store[1]. I personally believe this is because so many users are stuck with old Android devices where the store is no longer maintained. Folks like Let's Encrypt are unable to get a foothold[2], with so many decaying unmaintainable operating systems out there. Chrome & every other app doing 3rd party HTTPS have to start creating their own root certificate stores that they can maintain, since the dead operating system on such a vast % of devices will not. Tragic situation, in my opinion, and with so few unlockable phones, buyers have limited ability to maintain or repair their own devices. [1] https://www.chromium.org/Home/chromium-security/root-ca-policy https://www.chromium.org/Home/chromium-security/root-ca-poli... [2] https://letsencrypt.org/2020/11/06/own-two-feet.html https://letsencrypt.org/2020/11/06/own-two-feet.html
- cesarb 6y agoA scary warning might not be an issue for more technical users like us, but for a non-technical user, it's a relevant obstacle. A non-technical user does not have the knowledge and experience to know whether the warning is legitimate or not. In the worst case, the user learns to ignore that type of warning from then on, which only leads to the warning being made harder and harder to ignore (we're in that treadmill already; this warning used to be much less scary and much easier to ignore).
- zozbot234 6y agoNon-technical users should rely on their local IT support to address issues such as this. We're talking about OpenWRT configuration here, which is quite a "relevant obstacle" anyway for other reasons.
- cma 6y agoThis breaks for web sockets in Safari but not Chrome.