6 ms·
I use mkcert [1] with great success - it's easy to setup locally trusted certs which I load onto my router and other devices. [1]: https://github.com/FiloSotti
by arkadiyt 6y ago
I use mkcert [1] with great success - it's easy to setup locally trusted certs which I load onto my router and other devices.
[1]: https://github.com/FiloSottile/mkcert https://github.com/FiloSottile/mkcert
- wtallis 6y agoThat seems like a nifty tool, but it doesn't seem to do anything to address the difficulty of getting your private CA trusted on more than one of your devices. I'd like to be able to access my router and switch configuration interfaces from more than one client PC, and perhaps even from a smartphone.
- nemosaltat 6y agoSame here. I run OpenWRT on my home routers, and your comment prompted me to do a quick web search. uacme looks promising for luci. I’d love to hear HN experiences with it.
- cpach 6y agoYou can copy the (public part) of the generated root certificate over to your other computers and smartphones.
- otabdeveloper4 6y agoYes, that is the hard part.
- exikyut 6y agoFWIW, tapping on .crt files in Chrome offers to open them with the certificate manager on Android, where it's then straightforward to install them. Unfortunately this also produces some very irritating (non-removable) notifications... >.< ...And I can't deny I was fetching the certificate from my PC across the room over HTTP, not HTTPS. :/
- octorian 6y agoGetting your private CA trusted on a smartphone seems to keep getting more and more difficult and/or annoying with every iteration of the various mobile OSes. If it was possible to make a private CA cert that was only valid for hosts under a single domain, and then for mobile devices to STFU about you wanting to install it (as it wouldn't be as "risky" from their POV), life would be a little easier.
- namibj 6y agoIt's actually possible to do so, but many non-browser/mainstream cert validation libraries have a habit of just ignoring that restriction.