Yep. But CA's typically put them in both anyway.On the other hand, if every site appears within the same domain (e.g. foo.domain.com, bar.domain.com, baz.domain.com), it might be better to get a domain cert that contains "*.domain.com".
-Joe On Nov 4, 2005, at 3:17 PM, Goetz Babin-Ebell wrote:
Joseph Oreste Bruni wrote:You can have as many commonNames as you want. That goes for subjectAltName fields too. I do that on an apache server (not using TLS) that needs to host more than one SSL site. Every browser I've used is okay with certs. that have multiple CN's.But he should use the subjectAltName extension. Using the CN is deprecated.On Nov 4, 2005, at 6:27 AM, [EMAIL PROTECTED] wrote:I know it isn't the correct way to do stuff, but since it's only test serverI want to do the following:I have a server with 2 ethernet cards, one for internal net, one for the external. Both have different IP-addresses and different domain names (external has even some c-names). What I want is one certificate whichcontains all domains, c-names and ip addresses...Bye Goetz -- DMCA: The greed of the few outweighs the freedom of the many
smime.p7s
Description: S/MIME cryptographic signature
