http://bugs.winehq.org/show_bug.cgi?id=34388
--- Comment #2 from Charles Davis cdavis5x@gmail.com 2013-09-02 00:55:25 CDT --- Created attachment 45818 --> http://bugs.winehq.org/attachment.cgi?id=45818 Patch to fix Star Citizen signature verification bug
I can confirm that this is present on Mac OS as well. (Yes, I know, Wine64 doesn't work on Mac OS yet, but I'm working on it. The installer and launcher are still 32-bit executables, though, so I decided to give 'em a shot to see if I could even install it.)
The launcher executable is signed. You can verify this with winedump(1)--the SECURITY data directory will be non-NULL. Embedded within the signature is the Certificate Authority needed to verify the signature. When it is run, it attempts to import this certificate locally before manually verifying the signature. But one of the items in the certificate is unknown to Wine--its ASN tag is ASN_CONSTRUCTOR|ASN_UNIVERSAL|0x11 (0x31). (You can see this by attempting to run the launcher with +cryptasn. Look for "tag 31 doesn't match expected 30" in the output.) It doesn't seem to contain anything important, because just skipping this item causes the import--and thus, the signature verification--to succeed.
I've attached a patch that should hopefully fix this (it did for me), but I won't be submitting this to wine-patches until I come up with a good test case (i.e. one that can be embedded in Wine's test suite). Try it and see if it works for you, too.