http://bugs.winehq.org/show_bug.cgi?id=4781
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|winsock |crypt32
--- Comment #30 from Juan Lang juan_lang@yahoo.com 2009-02-15 15:20:50 --- (In reply to comment #29)
I haven't said, it's a crypt32 bug, only i thinked so. MSN returned an error in XP mode, 8009000a; After a quick googling i found this on msdn (http://msdn.microsoft.com/en-us/library/aa915314.aspx) possibly related. It tells, 8009000a error code is NTE_BAD_TYPE, Invalid type specified. But it can be totally unrelated.
Thank you, that's useful. The last few lines of the WinXP log are: trace:crypt:CryptImportKey (0x177830, 0xde62b0, 36, 0x0, 00000100, 0x32f99c) trace:crypt:RSAENH_CPImportKey (hProv=00000004, pbData=0xde62b0, dwDataLen=36, hPubKey=00000000, dwFlags=00000100, phKey=0x2084bc) trace:crypt:CryptReleaseContext (0x177830, 00000000) trace:crypt:CryptReleaseContext (0x177830, 00000000) fixme:imm:ImmGetOpenStatus (0x176860): semi-stub
If I were to guess, I'd say CryptImportKey is getting passed a blob type it doesn't recognize. From dlls/rsaenh/rsaenh.c: switch (pBlobHeader->bType) { (snip) default: SetLastError(NTE_BAD_TYPE); /* FIXME: error code? */ return FALSE; }
Some more traces probably need to be added to determine what's happening. Probably this would be an rsaenh bug, but lacking that as a component I'll switch it back to crypt32.