3 ms·
Sometimes 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
by viraptor 7y ago
Sometimes 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).
- the_duke 7y agoThen just use a wildcard cert.
- viraptor 7y agoWildcard certs are a security ops nightmare. You really don't want to throw the private key for that around to every small project, and you need some good, automated way of rolling them across multiple services. Doable, but if you can avoid this, it's a better to avoid.
- GordonS 7y agoThis 100x - in just about any organisation of any size, if you use a single wildcard cert for all internal services, then it's inevitable that the private key will end up in the hands of an employee that shouldn't have it.