4 ms·
That would be a bad use IMO. Letsencrypt solves any need for legitimate certificates.
by vbezhenar 7y ago
That would be a bad use IMO. Letsencrypt solves any need for legitimate certificates.
- layoutIfNeeded 7y agoLol. Sure, company sysadmins will run certbot on their mainframes.
- vbezhenar 7y agoThere are plenty of clients for letsencrypt, including even Bash ones. That should not be a problem.
- michaelt 7y agoLetsencrypt only issues certs for publicly accessible hosts. If you've got a bunch of intranet servers / REST services / whatever that are firewalled from the public internet, you're out of luck.
- jupp0r 7y agoThats incorrect, you can verify using DNS zone records, so the server can be as firewalled or air gapped as you want.
- cat199 7y ago> Letsencrypt solves any need for legitimate certificates. ... unless you want any private keys to be personally signed and or generated by bob & alice over in security after checking some boxes in an internal audit form, or any other number of company-internal schemes involving signing and encryption of business-specific data
- vbezhenar 7y agoYou're generating private key securely. You're generating CSR which contains public key and signed by that private key and now you need to move that CSR from private location to a public location. But that's not bad, it does not contain anything that could be compromised and your private key is kept safe. Then you're using letsencrypt to issue that certificate using that CSR and keep using that CSR (it does not expire) to renew certificate. All that time private key is kept in safety and is only used by your webserver. Letsencrypt allows you to generate legitimate certificate for internal websites without any compromise on security. The only use-case that's not possible with Letsencrypt is to issue certificate for IP address.
- technion 7y agoI don't think it's a bad use. When I logon to my SAN or UPS web interfaces, I don't want to type https://ups01.publicDNSdomain.com https://ups01.publicDNSdomain.com, and visit a site with a CT logged certificate. It's an absolutely internal thing and every Active Directory domain already has an (ideally) non-externally resolved DNS domain setup for use. You've already got an internal CA and deployed your own root because there's a series of Microsoft services that work best this way, so it makes a lot of sense to continue to use rather than trying to introduce Lets Encrypt in this scenario.
- vbezhenar 7y agoYou don't have to serve that website publicly or even set up DNS records. You only need to set up DNS verification to serve one public TXT record for letsencrypt. Everything else could be internal. Letsencrypt certifies that you own domain. You can do anything with that domain.
- technion 7y agoI'm aware you can use Lets Encrypt that way, I just don't agree that it's bad use of an internal PKI to use it as an alternative.
- vbezhenar 7y agoWell, it's unnecessary work to install and maintain that internal CA. Keeping CA key safe is very important, because leaked key might lead to your internal connections to, e.g., Google be compromised, so it's like keeping a bomb inside your building. If you already have that internal PKI, you can use it, sure, but I still think that it's a bad idea to use it only for internal websites.
- viraptor 7y agoSometimes you don't want to make that information public though. For security (you don't want to publish your whole tech stack information) and secrecy (you don't want to publish registration of halflife3.internal.valve.com).