http://bugs.winehq.org/show_bug.cgi?id=22709
--- Comment #2 from Juan Lang juan_lang@yahoo.com 2010-05-15 19:18:33 --- Sigh. The trouble is, the certificate is invalid for tools.google.com according the RFCs: * is not a valid character in DNS names, therefore it's invalid in the DNS name form in the alternate name extension. If an alternate name extension is present, it MUST be checked (and * doesn't match anything.) So, either crypt32 is non-compliant, or winhttp is. Tests needed, of course.