I have a working win32 binary created using PyInstaller, but when I sign the binary using the Windows SDK signtool.exe, my application stops working.
The message it prints at the command prompt is: (application) has bad magic! It appears that this is in launch.c where it displays the "bad magic" message. I have looked at the binary diff between version of the signed and unsigned executable, and the digital signature block is appended to the end of the file. In launch.c I can see that it seeks to the end of the file to read the "cookie" to determine the size of the data block added to the exe. That "cookie" gets stomped on by the digital signature, or at least it is no longer the very end of the binary once the file is signed. Is there any way around this "bad magic" when trying to digitally sign a PyInstaller binary? Thanks, - Bryan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
