4 ms·
This is not true, you can set your host to trust a self signed certificate without much difficulty. Check out this tool for example https://github.com/FiloSotti
by isignal 6y ago
This is not true, you can set your host to trust a self signed certificate without much difficulty. Check out this tool for example https://github.com/FiloSottile/mkcert https://github.com/FiloSottile/mkcert (prev discussion at https://news.ycombinator.com/item?id=17748208 https://news.ycombinator.com/item?id=17748208)
- colejohnson66 6y agoSelf signing doesn’t let the world access my website without some scary warning.
- rblatz 6y agoThat’s irrelevant to this discussion about hosting sites on a LAN with no internet access. If you need https on the public internet you need a trusted cert.
- bildung 6y agoDon't think personal LAN, think e.g. industrial automation: Many sensible companies want modern sensor systems that provide REST APIs and so on, but don't want those to access the internet. The hosts in this case often are appliance-like devices from third parties.
- colejohnson66 6y agoBut that’s my point, and many others’. Sure, we can self sign, but it’s useless for the WWW. You’re forced to pay up to one of the few certificate providers. Thankfully, Let’s Encrypt has made it free and easier, but it’s not a no-brainer.
- midasuni 6y agoI would like to trust a given root very for only a specific domain (and sub domain) I.e *.int.mycorp.com, but not www.mybank.com Browsers don’t let me do that, it’s either app or nothing. X509 name constraints aren’t great either and don’t give me, the browser operator, the power.
- forgotmypw17 6y agoHow long do you think it would take someone who has never been to HN? I don't think they would even know the option exists.