Hi, > Marko Asplund [SMTP:[EMAIL PROTECTED]] asked: [...] > i'm a bit confused by this message. the common name field in the > certificate signing request is CN=puppa.huuhaa.org. how can it be that > browsers would give name mismatch warnings if the URL used is not > https://puppa.huuhaa.org/? don't browsers match server name against the > certificate's CN field's value and not the URL through which the server is > accessed? > You can have multiple DNS names point to the same server address, i.e. www.domain.net and www.other-domain.net resolve to the same address. Now if your server cert at that address is made out for www.domain.net but you access the site via www.other-domain.net, the domain names don't match. Thawte's issue is probably with the current trend to have both domain.name and www.domain.name DNS entries for the same site. MfG, -- Thomas Bätzler, System Administrator, Network Operations EMEA Harbinger, e-Business Connectivity Group, a part of Peregrine Steinhäuserstraße 22 phone: +49-721-98143-110 D-76135 Karlsruhe / Germany fax: +49-721-98143-196 ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
