10 ms·
You can make a self-signed CA certificate any time you want, and anything with a browser will let you import it AFAIK. This can be locked down on corporate Win
by tenebrisalietum 4y ago
You can make a self-signed CA certificate any time you want, and anything with a browser will let you import it AFAIK. This can be locked down on corporate Windows machines via Group Policy, so this really only affects computers already behind myriad layers of HTTP security layer gunk. You'll just have to access your home streaming server from your phone over the guest Wi-Fi.
- superkuh 4y agoYou're right about that use case. And the business people are right about their internal use cases. But those are not what I'm talking about. It effects human people trying to host a generally accessible public website. Since HTTP/3 using QUIC cannot establish a connection to a site without a cert the public cannot access my hypthetical HTTP/3 website unless I get a corporation to continiously approve of it (ie, letsencrypt). Distributing my self signed CA chain to the browser mechanisms appropriate for it for every random person around the world that would try to load to my website is not realistic. For now HTTP 1.1 is still supported by all browsers. But it won't be long till it is phased out "for security" when it no longer makes profit-sense for megacorp browsers to support it (ie, none of their services require it). And when that happens it will no longer be possible to host a website without corporation permission. That's bad.
- deleted 4y ago[deleted]