Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: SB10 Feature Request

  1. #1

    Default SB10 Feature Request

    It could be useful to some folks if the compiler captured the
    pertinant parts of the output from SignTool, especially the error
    messages.

    e.g. instead of "Error 1", having the output below could save someone
    some time, some time, sometimes<g>:

    SignTool Error: SignedCode::Sign returned error: 0x800700C1
    %1 is not a valid Win32 application.
    SignTool Error: An error occurred while attempting to sign:
    C:\MyAppDist\MyApp.exe


    Showing the entire signtool commandline (as generated/passed by SB10)
    might also be useful when errors are encountered.

    Thanks.

    Jeff Slarve
    www.jssoftware.com

    Ones and Zeros are my Heroes

  2. #2

    Default Re: SB10 Feature Request

    Hi Jeff,

    > It could be useful to some folks if the compiler captured the
    > pertinant parts of the output from SignTool, especially the error
    > messages.
    >
    > e.g. instead of "Error 1", having the output below could save someone
    > some time, some time, sometimes<g>:
    >
    > SignTool Error: SignedCode::Sign returned error: 0x800700C1
    > %1 is not a valid Win32 application.
    > SignTool Error: An error occurred while attempting to sign:
    > C:\MyAppDist\MyApp.exe

    Unfortunately, you can't catch this return code at all.

    There are only three possible return values (exit codes):

    0 = Execution was successful.
    1 = Execution has failed.
    2 = Execution has completed with warnings.

    > Showing the entire signtool commandline (as generated/passed by SB10)
    > might also be useful when errors are encountered.

    Good idea!

    Friedrich

  3. #3

    Default Re: SB10 Feature Request

    Hi Friedrich -

    >
    >
    >Unfortunately, you can't catch this return code at all.
    >
    >There are only three possible return values (exit codes):
    >
    >0 = Execution was successful.
    >1 = Execution has failed.
    >2 = Execution has completed with warnings.

    Rick Martin wrote a Clarionmag article about capturing output
    https://clarionmag.jira.com/wiki/spa...ag-2008-01.pdf


    >> Showing the entire signtool commandline (as generated/passed by SB10)
    >> might also be useful when errors are encountered.
    >
    >Good idea!

    Jeff Slarve
    www.jssoftware.com

    Ones and Zeros are my Heroes

  4. #4

    Default Re: SB10 Feature Request

    > Rick Martin wrote a Clarionmag article about capturing output

    That is the problem. There is not any output.

    Only if you call some kind of command line prompt. There is no output if
    you use ShellExecute and "wait" for the signtool.exe termination.

    Friedrich

  5. #5

    Default Re: SB10 Feature Request

    > There is no output if you use ShellExecute and "wait" for the
    > signtool.exe termination.

    As far as I know <g>.

    Friedrich

  6. #6

    Default Re: SB10 Feature Request

    > Rick Martin wrote a Clarionmag article about capturing output
    > https://clarionmag.jira.com/wiki/spa...ag-2008-01.pdf

    I tried the link on different Win10 machines, but that's the only thing I
    see (it's sitting there for 10 minutes now).

    Friedrich
    Attached Images Attached Images  

  7. #7

    Default Re: SB10 Feature Request

    Yeah. Been there.<g>

    If you download the PDF, you can view it.

    Jeff Slarve
    www.jssoftware.com

    Ones and Zeros are my Heroes

  8. #8

    Default Re: SB10 Feature Request

    >> Showing the entire signtool commandline (as generated/passed by SB10)
    >> might also be useful when errors are encountered.
    >
    >Good idea!

    But then won't you be disclosing the Certificate password in clear text? And some my
    not want that!

    JohnG

  9. #9

    Default Re: SB10 Feature Request

    Leaving that part out or replacing with ****** would be ok.

    At least, on the EV cert, you leave the password blank and let safenet
    manage the password.

    Not sure if SB passes the password through the commandline or stuffs
    into a dialog that pops up. But if it's passed through the command
    line, of course it would be best to obscure on the compile log.

    Jeff Slarve
    www.jssoftware.com

    Ones and Zeros are my Heroes

  10. #10

    Default Re: SB10 Feature Request

    Hi Friedrich,

    > Unfortunately, you can't catch this return code at all.

    I have never used SignTool on the command line, but is it possible to
    redirect the output to a dummy file in temp folder and then upon
    receiving 1 or 2 check for that file for additional information? I.e.

    signtool.exe ... > %temp%/signtool_result.txt

    Best regards,

    --
    Arnor Baldvinsson
    Icetips Alta LLC

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •