http://bugs.winehq.org/show_bug.cgi?id=27168
--- Comment #21 from Ilya Konovalov aragaer@gmail.com 2011-09-14 11:39:41 CDT --- (In reply to comment #20)
(In reply to comment #16)
I've also found a few bugs in crypt32 during my investigation. The patch could be found here: https://gist.github.com/1209583
Actually, the bulk of this patch appears incorrect, according to the test case at http://source.winehq.org/source/dlls/crypt32/tests/cert.c#L588 So don't send that one ;)
If nonexistent, searches for the szOID_SUBJECT_KEY_IDENTIFIER extension. If that fails, a SHA1 hash is done on the certificate's SubjectPublicKeyInfo member to produce the identifier values. (http://msdn.microsoft.com/en-us/library/aa376079(v=vs.85).aspx)
As of two other changes in that patch they don't really change anything.
Also I don't really know how to send patches at all so I'll pass for now anyway 8)
Currently I'm thinking on freeing the temporary store. Ref counters there are quite a mess.