Einzelnen Beitrag anzeigen

generic

Registriert seit: 24. Mär 2004
Ort: bei Hannover
2.416 Beiträge
 
Delphi XE5 Professional
 
#2

AW: Thawte Code Signing will nicht

  Alt 24. Jun 2011, 11:14
Du solltest auf das neue signtool aus dem SDK wechseln.

Dort kannst du mit /f auch eine PFX Datei angeben.


Code:
signtool sign /?
Usage: signtool sign [options] <filename(s)>

Use the "sign" command to sign files using embedded signatures. Signing
protects a file from tampering, and allows users to verify the signer (you)
based on a signing certificate. The options below allow you to specify signing
parameters and to select the signing certificate you wish to use.

Certificate selection options:
/a         Select the best signing cert automatically. SignTool will find all
            valid certs that satisfy all specified conditions and select the
            one that is valid for the longest. If this option is not present,
            SignTool will expect to find only one valid signing cert.
/ac <file> Add an additional certificate, from <file>, to the signature block.
/c <name>  Specify the Certificate Template Name (Microsoft extension) of the
            signing cert.
/f <file>  Specify the signing cert in a file. If this file is a PFX with
            a password, the password may be supplied with the "/p" option.
            If the file does not contain private keys, use the "/csp" and "/k"
            options to specify the CSP and container name of the private key.
/i <name>  Specify the Issuer of the signing cert, or a substring.
/j <dll>   Name of the DLL that provides attributes of the signature.
/jp <param> Parameter to be passed to the DLL.
/n <name>  Specify the Subject Name of the signing cert, or a substring.
/p <pass.> Specify a password to use when opening the PFX file.
/r <name>  Specify the Subject Name of a Root cert that the signing cert must
            chain to.
/s <name>  Specify the Store to open when searching for the cert. The default
            is the "MY" Store.
/sm        Open a Machine store instead of a User store.
/sha1 <h>  Specify the SHA1 hash of the signing cert.
/u <usage> Specify the Enhanced Key Usage that must be present in the cert.
            The parameter may be specified by OID or by string. The default
            usage is "Code Signing" (1.3.6.1.5.5.7.3.3).
/uw        Specify usage of "Windows System Component Verification"
            (1.3.6.1.4.1.311.10.3.6).

Private Key selection options:
/csp <name> Specify the CSP containing the Private Key Container.
/kc <name> Specify the Key Container Name of the Private Key.
/snk <file>   Specify the SNK file containing the SN Private Key.
/sncsp <name> Specify the CSP containing the SN Private Key Container.
/snkc <name>  Specify the Key Container Name of the SN Private Key.
/snks <1 | 2> Specify the SN Private Key to be used (1 = AT_KEYEXCHANGE,
               2 = AT_SIGNATURE, default is AT_SIGNATURE).

Signing parameter options:
/d <desc.> Provide a description of the signed content.
/du <URL>  Provide a URL with more information about the signed content.
/t <URL>   Specify the timestamp server's URL. If this option is not present,
            the signed file will not be timestamped. A warning is generated if
            timestamping fails.

Other options:
/ph        Generate page hashes for executable files if supported.
/nph       Suppress page hashes for executable files if supported.
            The default is determined by the SIGNTOOL_PAGE_HASHES
            environment variable and by the wintrust.dll version.
/q         No output on success and minimal output on failure. As always,
            SignTool returns 0 on success, 1 on failure, and 2 on warning.
/v         Print verbose success and status messages. This may also provide
            slightly more information on error.
Coding BOTT - Video Tutorials rund um das Programmieren - https://www.youtube.com/@codingbott
  Mit Zitat antworten Zitat