←back to thread

238 points edent | 1 comments | | HN request time: 0.211s | source
Show context
imadethis ◴[] No.29809315[source]
This seems like a perfect use case for wild card certs, especially if you have internal sites on a different (sub) domain from your prod servers. Yes, multiple servers have the same private key, but when the alternative is self-signed or no encryption, that is an easy trade off for me.
replies(3): >>29809569 #>>29811047 #>>29812720 #
justusthane ◴[] No.29809569[source]
I don't know how LE does it, but at least with DigiCert (and I assume other commercial CAs), servers sharing the same wildcard cert don't have to share a private key. You generate a separate CSR from each server, and then request a duplicate copy of the wildcard cert using that CSR. That way they can have different SANs as well.
replies(2): >>29809759 #>>29811861 #
zrail ◴[] No.29809759[source]
Wildcard certs are (only?) issued from DNS-01 challenges. As long as the requester can satisfy the DNS challenge ACME doesn't care about key uniqueness.
replies(2): >>29809856 #>>29810793 #
dsr_ ◴[] No.29809856[source]
Right. If you control the DNS, you can point names at any IP address and get appropriate certs for them. Therefore, you must protect your DNS infrastructure.
replies(1): >>29810144 #
Hamuko ◴[] No.29810144[source]
Isn't the need to protect your DNS infrastructure pretty obvious anyways even when ignoring certificate validation?
replies(2): >>29810863 #>>29818074 #
1. fomine3 ◴[] No.29818074[source]
Obvious, but tend to be missed on small deployments.