Windows Defender code signing #1272
Unanswered
RussNelson
asked this question in
Q&A
Replies: 1 comment 3 replies
-
My speculation is that cx is looking past the end of the executable (or what it thinks is the end), and is trying to parse it. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a frozen application (updated using esky) which needs to be signed so it can run on Windows 10 without Windows Defender having a cow. I can successfully sign the executable and Windows Defender ceases objecting to it. When I run it, I get a cx_Freeze fatal error: "Cannot find zipimporter instance". I speculate that it's trying to look inside the file for something that got overwritten [update: it isn't]. I presume this is because the signed executable has extra data at the end, as well as a few values in the header modified:
00000141 C7 79
00000142 66 CE
00000143 13 14
00000181 00 10
00000182 00 D2
00000183 00 13
00000185 00 F8
00000186 00 11
0141 - 0144 is the checksum of the Microsoft Portable Executable header.
0181 - 0184 is the offset to the signing data.
0185 - 0186 is the length of the signing data.
I still haven't found how cx writes the .exe and why signing it screws up something. Still working on that. All hints gladly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions