4 ms·
I believe the intent here is: * If you want an SSL certificate for, say, your printer * And you don’t want to expose your printer’s port 80 to the public inte
by michaelt 1y ago
I believe the intent here is:
* If you want an SSL certificate for, say, your printer
* And you don’t want to expose your printer’s port 80 to the public internet because you’re not stupid
* And you don’t want to put your DNS credentials onto your printer either, because again, you’re not stupid
* And you don’t want to pay for a certificate with a longer validity, because it’s a home printer, so you’re stitch with monthly cert rotations
* And you’ve embraced the reality that one can delegate SSL not just to CAs, but also to other third parties. Usually the likes of AWS & cloudflare - but why stop there?
Then this product is what you need!
- eternauta3k 1y agoWhy not sign it yourself?
- woodruffw 1y agoMost people find the user experience of self-signed certificates much worse. The developer experience for local issuance isn't great, although mkcert does a really great job of smoothing the parts that can be smoothed[1]. [1]: https://github.com/FiloSottile/mkcert https://github.com/FiloSottile/mkcert
- xp84 1y agoI started but haven't yet completed a project to use mkcert on a home server, and get all devices in the house to trust it as a CA for things such as printers and "internal tools" for my family such as Jellyfin, etc. This would probably be easier if I was organized enough to use at least minimal MDM features on the family's devices though, so I haven't actually completed this project yet.
- toast0 1y ago> * If you want an SSL certificate for, say, your printer Ummmm why does my printer need a certificate?
- mholt 1y agoIf you can't trust your network, you'll want encryption, regardless of devices on it.
- Palomides 1y agoif you can't trust your network, everything needs to be public internet level hardened anyway, so why not just directly use letsencrypt?
- Hackbraten 1y agoBecause you don't want to expose your printer to the public Internet?
- fxtentacle 1y agoThen you need to make your network trustworthy first.
- Hackbraten 1y agoWhy?
- fuckinpuppers 1y agoIsn’t that what dns challenge can be used for?
- michaelt 1y agoWell yes, you've just hit on why this is a rather niche product. You get a handful of somewhat questionable benefits. If for some reason your guests are visiting your printer's administration page, they won't have to click through a scary warning page. If someone is somehow sniffing all the traffic within your home network they won't be able to get your printer's administrative password. But the main reason is some homelab enthusiasts are like bodybuilders at the gym - taking on tasks that seem Sisyphean to outsiders, for fun and to build their strength.
- unsnap_biceps 1y agoAre there any printers that actually run acme where this is even a consideration?
- weddpros 1y agoI think it's more a matter of scale. If you need SSL certificates for hundreds of appliances and you want to manage it, rather than hack it, that's the product you need.