> Of course you could > get away with it by having only sub-domains, like thishost.domain.com, > anotherhost.domain.com and so on, and the certificate having > *.domain.com. > Interesting. and how do you generate a certifcate for a whole domain.com ? As far as I know CA like verisign does not support things like this : from "http://www.verisign.com/support/ssl-certificates-support/page_dev019500.html"; --Common Name The Common Name is the Host + Domain Name. It looks like "www.company.com" or "company.com". VeriSign certificates can only be used on Web servers using the Common Name specified during enrollment. For example, a certificate for the domain "domain.com" will receive a warning if accessing a site named "www.domain.com" or "secure.domain.com", because "www.domain.com" and "secure.domain.com" are different from "domain.com".-- Maybe some other CA supports it... I wonder if CACERT.org do... Can you point on some more informations about this ? Thanks. Jerome --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|