Re: Can't Code Sign a Particular .MSI

On Apr 1, 1:48*pm, "Adrian Accinelli"
<hclnospamali...@newsgroup.nospam> wrote:
> "Superfreak3" <Matt.Wal...@synergis.com> wrote in message
>
> news:57a2beb6-8c31-40ee-9bd7-767e7c7517b9@13g2000hsb.googlegroups.com...
>
>
>
>
>
> > On Apr 1, 9:09 am, Superfreak3 <Matt.Wal...@synergis.com> wrote:
> >> On Apr 1, 9:06 am, Superfreak3 <Matt.Wal...@synergis.com> wrote:
> >>> On Mar 31, 6:37 pm, "Adrian Accinelli"
> >>> <hclnospamali...@newsgroup.nospam> wrote:
> >>>> "Superfreak3" <Matt.Wal...@synergis.com> wrote in message
> >>>>news:e15d0c41-d773-46ef-95de-95a70c6ad330@m36g2000hse.googlegroups.com..
> >>>> ..
> >>>>> On Mar 28, 12:22 pm, Superfreak3 <Matt.Wal...@synergis.com> wrote:
> >>>>>> Hello there,
> >>>>>> I have various .msi'sthat I need to digitallysignand can do so to
> >>>>>> most. There is oneparticular.msithat I cannotsignand Ican'tfor
> >>>>>> the life of me figure this out.
> >>>>>> I'm using Wise Installation Studio to generate the .msiand there isa
> >>>>>> Digital Signature area in that application that allows me to
> >>>>>> enter the authenticode information. Again, for the most part,
> >>>>>> this works fine, except for this one.
> >>>>>> I also try signing it with SignCode.exe, but that to fails for
> >>>>>> thisparticularfile.
> >>>>>> Does anyone have any idea what could be causing this to fail?
> >>>>>> Any help would be GREATLY APPPRECIATED!
> >>>>>> THANKS IN ADVANCE!
> >>>>> Early testing on my part has indicated that size of the file being
> >>>>> signed has something to do with it. I stripped some 'stuff' from the
> >>>>> problematic .msiand was then able tosignit without problem.
> >>>>> Currently, the problematic .msisits at over 400 MB. Does anyone know
> >>>>> of any file size restrictions in signing .msi's?
> >>>> How are you determining that the signing failed? Using
> >>>> "signtool.exe verify /v your_file.MSI"?
> >>>> I know that on Windows XP any file over 400MB is abandoned(?) or
> >>>> at least not processed fully by explorer for file properties
> >>>> purposes and ICONs. For instance for an .EXEs > 400MB in size
> >>>> you'll notice that ICONs do not show up correctly for them. In
> >>>> addition doing properties on that same EXE won't provide all
> >>>> details including any digital signatures it might have. But if you
> >>>> go to a Vista machine and look at the same file you will notice
> >>>> that both the real ICON and all file properties are fully exposed
> >>>> including digital signature tab.
> >>>> You can find signtool.exe in VS2005
> >>>> ProgFiles\Vc80\Common7\Tools\Bin or in the latest SDK
> >>>> <root>\bin\SelfSign.
> >>>> Sincerely,
> >>>> Adrian Accinelli- Hide quoted text -
> >>>> - Show quoted text -
> >>> Yes, with signcode.exe it appears that the cutoff is 400 MB. If I
> >>> fully compress the files in my .msivia aparticularWise option,
> >>> the .msiis 398 MB and it is signable.
> >>> In looking to automate my build process, I though I would switch to
> >>> SignTool.exe as you can pass the certificate password via command
> >>> line. This, however seems more limiting with regard to size as I
> >>> cannot againsignthe higly copressed, 398 MB file.
> >>> Is there any way to pass the password via command line with
> >>> SignCode.exe or is there any way to work around the size limitation
> >>> with SignTool?
> >>> Anything Appreciated!
> >>> Thanks!- Hide quoted text -
> >>> - Show quoted text -
> >> Oh, also, about the indication of signing failure. I'm using Visual
> >> Build Pro and the failure notice is written to the output window as
> >> well as a log.
> >> When I attempted tosignthrough the SignCode wizard I get an on
> >> screen message that the process failed, but with no real clue from
> >> what I recall.- Hide quoted text -
> >> - Show quoted text -
> > I found this little handy utility to pass the password to SignCode.exe
> > in an excrypted file...
> >http://www.stephan-brenner.com/?page_id=9
>
> I have no problems signing large files (even 800MB+) with signtool.exe
> (version 6.0.6000.16386 -- from Vista equivalent WDK I believe). *It also
> does not require any prompts or use of any hacks to pass the password to a
> prompt window.
>
> The implementation of these signing tools is that they use copious amounts
> of temp folder space during signing so maybe your build machine is simply
> running of out temp space? *Try signing with 2X target file size in
> temporary space available.
>
> If it still fails show exactly the error provided by signtool.exe when
> dealing with the large file. *If you can manually get it to sign in command
> prompt then you can get most build tools to use it properly.
>
> Sincerely,
> Adrian Accinelli- Hide quoted text -
>
> - Show quoted text -

The version of signtool I was working with is 5.x. I guess I can try
to get the v6 .exe and try signing with that.

I don't know what you mean by....

"Try signing with 2X target file size in temporary space available."

"Superfreak3" <Matt.Walker@synergis.com> wrote in message
news:c236533e-75a6-4f94-a4e7-7581c761f99c@a23g2000hsc.googlegroups.com...

< snip >

>> - Show quoted text -
> The version of signtool I was working with is 5.x. I guess I can try
> to get the v6 .exe and try signing with that.
> I don't know what you mean by....
> "Try signing with 2X target file size in temporary space available."

If your target file is 400 MB try signing with at least 800MB free on the
volume that contains your temp folder. Use process monitor (filter on
signtool.exe) to see which folder/volume is being used for temp files during
your build process in case you redirect somewhere other than your typical
%temp% folder.

Sincerely,
Adrian Accinelli