PDA

View Full Version : installer seems to be unsigning my exe



NewsArchive
04-29-2014, 01:43 AM
Ok,

This worked last week... and now.. not so much. This is a super simple
install. I'm code signing an exe... the log says it works, but it doesn't
get signed. The install does get signed so I know the signing mechanism
works... plus

I watched the file go from 720k to 728k then back to 720k. So, I added a
copy right after the signing so it copied the just signed exe into another
folder.. sure enough, the file was signed... but somewhere after the install
program is 'un-signing' the file.

Any ideas?

Thanks

--
Ray Rippey
VMT Software - http://www.workordersoft.com

NewsArchive
04-29-2014, 01:44 AM
So, I decided on this workaround.. I copied the file into another folder
after the signing, then installed that file. Still don't know what would
cause SB to unsign the file... but it didn't unsign the file that I copied
into another folder... weird.

Ray

NewsArchive
04-29-2014, 01:44 AM
> So, I decided on this workaround.. I copied the file into another folder
> after the signing, then installed that file. Still don't know what would
> cause SB to unsign the file... but it didn't unsign the file that I copied
> into another folder... weird.

Ray

Check your install script and make sure that if you are adding a manifest
in SetupBuilder, that you are doing it BEFORE the script command to code
sign the exe.

Otherwise that could "unsign" the exe as it would be modifying the file
after the code signing was complete.

JAT...

Charles



--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

cjeByteMeSpammers@lansrad.com (remove the "ByteMeSpammers" to email me)
www.clarionproseries.com - ProScan, ProImage, ProPath and other Clarion
developer tools!
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms - Now with PNG support!
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

NewsArchive
04-29-2014, 01:45 AM
Ray,

> So, I decided on this workaround.. I copied the file into another folder
> after the signing, then installed that file. Still don't know what would
> cause SB to unsign the file... but it didn't unsign the file that I copied
> into another folder... weird.

This happens when you do not enable the "Permanent" option. If this
checkbox is not marked, the compiler leaves the original file untouched. The
compiler creates a temporary copy of the file and after script compilation
restores it to the original.

Friedrich

NewsArchive
04-29-2014, 01:45 AM
Ray

You probably don't have the Permanent flag set, so that SB code signs your source
EXE/DLL. Otherwise, it will make a temporary copy of the file, and code sign the
temporary copy which gets incorporated into the final install as a codesigned copy,
leaving your original un-signed as you are seeing.

So make it permanent. set the checkbox.

JohnG

NewsArchive
04-29-2014, 01:48 AM
I've been there too <g>

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.