http://bugs.winehq.org/show_bug.cgi?id=8996
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #7 from Juan Lang juan_lang@yahoo.com 2007-08-10 12:43:21 --- I should have been more careful with my last comment: it appears this does have something to do with crypto, after all. The following lines in the console are suspicious: fixme:wintrust:WinVerifyTrust 0xffffffff {00aac56b-cd44-11d0-8cc2-00c04fc295ee} 0x34d7cc fixme:crypt:CryptVerifyMessageSignature stub: 0x34d90c, 0, 0x1901780, 5360, (nil), 0x34d934, 0x34d930
Overriding wintrust gets the same behavior, without the WinVerifyTrust fixme (but the CryptVerifyMessageSignature fixme remains.)
Overriding crypt32 still gets repeating messages and no progress.
Anyway, there's evidence this is caused by either WinVerifyTrust or by lacking an implementation of CryptVerifyMessageSignature. I'll take the bug for now then.