http://bugs.winehq.org/show_bug.cgi?id=9685
--- Comment #29 from Juan Lang juan_lang@yahoo.com 2007-09-27 12:42:39 --- Actually, the real problem is just that I an idiot when I wrote that patch ;) I've sent in patches that fix that part of the problem (I was passing in the wrong pointer): http://www.winehq.org/pipermail/wine-patches/2007-September/044498.html http://www.winehq.org/pipermail/wine-patches/2007-September/044499.html
It still fails, however. From a +crypt log with these patches applied: trace:crypt:CryptDecodeObject (0x00010001, "1.3.6.1.4.1.311.2.1.12", 0x50004880, 1252019248, 0x00000000, (nil), 0x33c15c)
1.3.6.1.4.311.2.1.12 is SPC_SP_OPUS_INFO_OBJID, and the decode function for it, WVTAsn1SpcSpOpusInfoDecode, is a stub in wintrust.dll. The pointer and size look bogus, so I'm not sure they'd succeed even if it were implemented. The program appears to continue anyway.
Another suspicious line from the log: trace:crypt:CryptDecodeObject (0x00010001, #01f4, 0x30010102, 1728152112, 0x00000000, (nil), 0x33c164)
0x01f4 is 500 decimal, which is PKCS7_SIGNER_INFO. This is implemented, but the pointer and value look bogus. CryptDecodeObject will fail with CRYPT_E_ASN1_LARGE with a size this big. This appears to be the last bit of useful work crypt32 is doing, so the question is where the pointer and value come from.