Thanks for setting me straight on this.
I suppose I lack due diligence wrt this subject.
It is curious, the lack of predictibility MS have regarding not
published policies, but real world uses. Why would minor release
changes of the same product exhibit such a change?
Cheers
Bill Laakkonen
On 23 May 00, at 15:53, [EMAIL PROTECTED] wrote:
>
>
>
> >On Mon, 22 May 2000 [EMAIL PROTECTED] wrote:
> >> Hi All,
> >>
> >> It seems the latest version of IE 5.0 (5.00.2920.0000) on Windows
> >> 2000 Por no longer accept our wildcard certs from Thawte. These
> >> certs are like *.im1.net. Previous versions, and even Netscape 6
> >One can try querying MS to get implementation details.
> >..put their response on your website
> >Vadim
>
> Compare and contrast
>
> Netscape Navigator Server cert rules (wildcards OK) at :
> http://home.netscape.com/eng/security/ssl_2.0_certificate.html
>
> and
>
> Microsoft Internet Explorer Server cert rules (no wildcards allowed) at:
> http://www.microsoft.com/security/tech/certificates/structuring.asp#names
>
> (the magic words are "Microsoft does not support wildcarding for server
> names. ")
>
> This is, as far as I am aware, (and certainly since Feb 1999 when I last
> looked into this) always been the case.
>
> Paul
> --
> Paul Ford-Hutchinson : EMEA eCommerce application security :
> [EMAIL PROTECTED]
> MPT-6, IBM , PO Box 31, Birmingham Rd, Warwick, CV34 5YR +44 (0)1926 462005
>
>
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
