Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Post History
I've noticed that it's possible to use DNS Name multiple times, so that a TLS certificate will cover multiple domains. Alternatively, you could generate a separate cert for each domain. What are ...
#1: Initial revision
by
matthewsnyder
·
2024-03-28T21:34:08Z (8 months ago)
One cert with many domains, or one domain per cert?
I've noticed that it's possible to use `DNS Name` multiple times, so that a TLS certificate will cover multiple domains. Alternatively, you could generate a separate cert for each domain. What are the implications of choosing one approach or the other, in terms of security and maintainability? I'm sure actual certificate agencies restrict such things, and of course more certificates can be more expensive (unless you use a free CA like LetsEncrypt). In this case, I am asking about self-signed certificates for my own internal servers. So let's disregard purely administrative restrictions, and look at the practical consequences.