Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Vista Question

  1. #11

    Default Re: Vista Question

    You need to invoke the "#code-sign application" compiler directive for each
    file you want to sign.
    Code-signing will change the app's file date and will add roughly 3K to the
    file length.

    Jane

  2. #12

    Default Re: Vista Question

    Does this modify the original exe in my source directory or only the
    one that gets put into the installer? If only in the installer, is
    there a way I can get a copy of that to scan (so I can update the CRC
    for it in the security file that goes into the installer)?

    How important is it to sign the programs (as opposed to the
    installer)?

    Steve Rothkin

  3. #13

    Default Re: Vista Question

    Steve,

    If the "Permanent" option is not checked, it will *NOT* modify your original
    ..exe in your source directory. So your original file in your source folder
    is not code-signed, the file in your installer is code-signed.

    But your "CRC protection" is history with Microsoft Authenticode. If you
    code-sign an application file, this will change its binary contents. So
    your file CRC always changes if you code-sign.

    Does this help?

    Friedrich

    --
    Friedrich Linder
    Lindersoft
    www.lindersoft.com
    +1.954.252.3910

    "point. click. ship" - that's SetupBuilder 6
    Create Windows Vista ready installations in minutes

    -- Official Comodo Code Signing and SSL Certificate Partner

  4. #14

    Default Re: Vista Question

    OK, so I can "permanently" sign the executable and then rerun my
    program that calculates/stores the CRC (into an encrypted tps file)
    before the files are compressed into the installer.

    What are the advantages of code-signing my program? What are the
    disadvantages of NOT code-signing my program (and only code-signing
    the installer)?

    Steve Rothkin

  5. #15

    Default Re: Vista Question

    If you have a subscription to clarionmag.com, my current Vista-related
    article shows the type of warning screen users get if your app has any
    administrator-level requirements and isn't signed. Also, depending on your
    target audience, an administrator may have set security so that unsigned
    apps can't run at all.

    The next article in the series (about Vista's "virtual reality") will
    illustrate vividly some of the issues you can encounter if you don't use a
    Vista-aware manifest (which SB can also do for you... or you can link in
    yourself).

    Jane

  6. #16

    Default Re: Vista Question

    Great articles, Jane!

    --
    Russ Eggen
    www.radfusion.com
    IRC Info: www.radfusion.com/irc.htm
    Freebies: www.radfusion.com/downloads.htm

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
  •