Hello All.
For some time now our application was deployed as Single EXE file on windows. I do use the procedure outlined in the Packaging. txt So far I had no problems using Visual.exe versions 7.3 to 7.4.1 and 7.5. Also we do sign the resulting EXE using signcode.exe tool from the Windows SDK. Recently we moved to the VW 7.6. I go through the same procedure of adding image to the Exe using reshacker, which produces runnable EXE. However I can not sign it anymore, does anybody know what could be the problem ? In general, this is a question to the Cincom people - the visual.exe comes signed. What kind of tools do they use for signing and what version ? Any pointers are greatly appreciated. Truly, Mark Pirogovsky _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
I've found that after attaching an image to the executable with
reshacker, the crcs in the executable headers are invalid. Running UPX over it recreates the headers and then I can sign it. An added bonus is that you can use --lzma compression, which makes the executable even smaller. Cheers, Michael Mark Pirogovsky wrote: > Hello All. > > For some time now our application was deployed as Single EXE file on > windows. I do use the procedure outlined in the Packaging. txt > So far I had no problems using Visual.exe versions 7.3 to 7.4.1 and 7.5. > > Also we do sign the resulting EXE using signcode.exe tool from the > Windows SDK. > > Recently we moved to the VW 7.6. > > I go through the same procedure of adding image to the Exe using > reshacker, which produces runnable EXE. > > However I can not sign it anymore, does anybody know what could be the > problem ? > > In general, this is a question to the Cincom people - the visual.exe > comes signed. > > What kind of tools do they use for signing and what version ? > > Any pointers are greatly appreciated. > > Truly, > > Mark Pirogovsky > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Mark Pirogovsky-3
upx --compress-resources=0 --compress-icons=0 --lzma myprogram.exe
Mark Pirogovsky wrote: > Hello All. > > For some time now our application was deployed as Single EXE file on > windows. I do use the procedure outlined in the Packaging. txt > So far I had no problems using Visual.exe versions 7.3 to 7.4.1 and 7.5. > > Also we do sign the resulting EXE using signcode.exe tool from the > Windows SDK. > > Recently we moved to the VW 7.6. > > I go through the same procedure of adding image to the Exe using > reshacker, which produces runnable EXE. > > However I can not sign it anymore, does anybody know what could be the > problem ? > > In general, this is a question to the Cincom people - the visual.exe > comes signed. > > What kind of tools do they use for signing and what version ? > > Any pointers are greatly appreciated. > > Truly, > > Mark Pirogovsky > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Michael Lucas-Smith-2
Thanks Michael,
What puzzles me -- that it only happen with the latest 7.6b EXE, does work just fine with 7.4.1 and 7.5 exe(s). Probably there is something different in the way VW76b is compiled... Michael Lucas-Smith wrote: > I've found that after attaching an image to the executable with > reshacker, the crcs in the executable headers are invalid. Running UPX > over it recreates the headers and then I can sign it. An added bonus is > that you can use --lzma compression, which makes the executable even > smaller. > > Cheers, > Michael > > Mark Pirogovsky wrote: > >> Hello All. >> >> For some time now our application was deployed as Single EXE file on >> windows. I do use the procedure outlined in the Packaging. txt >> So far I had no problems using Visual.exe versions 7.3 to 7.4.1 and 7.5. >> >> Also we do sign the resulting EXE using signcode.exe tool from the >> Windows SDK. >> >> Recently we moved to the VW 7.6. >> >> I go through the same procedure of adding image to the Exe using >> reshacker, which produces runnable EXE. >> >> However I can not sign it anymore, does anybody know what could be the >> problem ? >> >> In general, this is a question to the Cincom people - the visual.exe >> comes signed. >> >> What kind of tools do they use for signing and what version ? >> >> Any pointers are greatly appreciated. >> >> Truly, >> >> Mark Pirogovsky >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >> >> > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Mark Pirogovsky-3
We also see problems with VW 7.6 and 7.6b VMs (visual.exe), which we
didn't see with 7.5 or 7.4d. We add the compressed image and icons to visual.exe with ResHacker, and then pass the result to a third party tool to wrap. The third party tool now gives an error ("code H" :->), whereas before it didn't. To get things to work we had to change the third party tool's options for how it deals with "data after program" (i.e. extra bytes on the end of the exe file after the actual executable and resources such as the image). I imagine this "data after program" is the manifest and code signature, which are present only in 7.6 and later - certainly they are at the end of the exe file. Is there a way to remove the manifest and code signature? As the documentation states, the Cincom ones shouldn't really be there anyway if we're redistributing the VM with our own program. Steve > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On > Behalf Of Mark Pirogovsky > Sent: 07 April 2009 22:42 > To: Michael Lucas-Smith > Cc: vwnc > Subject: Re: [vwnc] Packaging as Single EXE and signing it > > Thanks Michael, > > What puzzles me -- that it only happen with the latest 7.6b EXE, does > work just fine with 7.4.1 and 7.5 exe(s). Probably there is something > different in the way VW76b is compiled... > > > Michael Lucas-Smith wrote: > > I've found that after attaching an image to the executable with > > reshacker, the crcs in the executable headers are invalid. Running > UPX > > over it recreates the headers and then I can sign it. An added bonus > is > > that you can use --lzma compression, which makes the executable even > > smaller. > > > > Cheers, > > Michael > > > > Mark Pirogovsky wrote: > > > >> Hello All. > >> > >> For some time now our application was deployed as Single EXE file > >> windows. I do use the procedure outlined in the Packaging. txt > >> So far I had no problems using Visual.exe versions 7.3 to 7.4.1 > and 7.5. > >> > >> Also we do sign the resulting EXE using signcode.exe tool from the > >> Windows SDK. > >> > >> Recently we moved to the VW 7.6. > >> > >> I go through the same procedure of adding image to the Exe using > >> reshacker, which produces runnable EXE. > >> > >> However I can not sign it anymore, does anybody know what could be > the > >> problem ? > >> > >> In general, this is a question to the Cincom people - the > visual.exe > >> comes signed. > >> > >> What kind of tools do they use for signing and what version ? > >> > >> Any pointers are greatly appreciated. > >> > >> Truly, > >> > >> Mark Pirogovsky > >> > >> _______________________________________________ > >> vwnc mailing list > >> [hidden email] > >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > >> > >> > >> > > > > _______________________________________________ > > vwnc mailing list > > [hidden email] > > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > > > > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
I wonder would it be much to ask that Cincom release two versions of
Visual.exe one signed with manifest and another for the deployment i.e. without any extra information such as signature and manifest. BTW where that manifest came from -- I tried to use manifest tool from Windows SDK and has so much extra things in it... Where did you get that security token value? --Mark Steven Kelly wrote: > We also see problems with VW 7.6 and 7.6b VMs (visual.exe), which we > didn't see with 7.5 or 7.4d. We add the compressed image and icons to > visual.exe with ResHacker, and then pass the result to a third party > tool to wrap. The third party tool now gives an error ("code H" :->), > whereas before it didn't. To get things to work we had to change the > third party tool's options for how it deals with "data after program" > (i.e. extra bytes on the end of the exe file after the actual executable > and resources such as the image). I imagine this "data after program" is > the manifest and code signature, which are present only in 7.6 and later > - certainly they are at the end of the exe file. > > Is there a way to remove the manifest and code signature? As the > documentation states, the Cincom ones shouldn't really be there anyway > if we're redistributing the VM with our own program. > > Steve > > > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |