Authenticode

If you do not want your project Authenticode-signed, then none of this flowchart applies to your project.

The Certificate Verification tool checks the validity of a file signed with an Authenticode certificate.

Involves a system administrator performing a one-time installation of a publisher's Authenticode certificate on a client computer.

Digital certificates are a core component of the Microsoft Authenticode authentication and security system.

Assemblies can carry full Microsoft Authenticode signatures in addition to a strong name.

Note that if you want to sign a file with both a strong name and an Authenticode digital signature you must assign the strong name first.

The file registered as the ActiveX control must be signed with Authenticode technology.

A publisher whose Authenticode certificate has been added to a certificate trust list (CTL) on a client computer.

Specifies an Authenticode certificate file to be used to sign the files.

A basic constraint of a certificate in the signature failed for Authenticode.

A purpose specified in a certificate (signing or issuer) makes it invalid for Authenticode.

The public key of a valid Authenticode signature.

Authenticode signatures include a certificate that establishes trust.

Signature is not trusted by Authenticode with the current policy settings.

Creates an Authenticode time-stamp signature for a signed file.

Authenticode is a standard part of the Windows operating system.

For more information about the Authenticode signing technology, see "Introduction to Code Signing" in the Platform SDK documentation.

Two types of evidence, strong names and Authenticode publishers, are based on cryptographic keys and digital signature technology.

To sign a file with an Authenticode digital signature.

The extension in a certificate means the certificate can not be used for Authenticode .

In Smart Device CAB projects, select Authenticode Signing, and then click Select from Store.

Assigning the Authenticode signature first breaks the strong name.

There are various types of Authenticode certificates, each once configured for different types of signing.

Describes how Authenticode technology is used in trusted application deployment.

Specifies whether output files will be signed using Authenticode signing.

In addition, the deployment manifest should be signed using Authenticode signing.

In the Property Pages dialog box, check Authenticode signature.

Signature is not trusted by Authenticode.

Explains how Authenticode is used in ClickOnce application deployment.

For more information, see the CertMgr section in the topic, "Signing and Checking Code with Authenticode, " in the MSDN Library.

The dialog gives you the option to install and run the PE file even though an Authenticode signature could not be found.

Describes the use of Authenticode signing in deployment.

For more information, see the CertMgr section in Signing and Checking Code with Authenticode.

Software publisher signature; that is, the Authenticode signer of the code.

In order to prevent user confusion, you can update these images to reflect the new Authenticode user interface (UI).

Signing Managed Code with a Microsoft Authenticode Signature

Vulnerability in Authenticode verification could allow remote code execution

Code Signing Certificate for Microsoft Authenticode

For more information about Authenticode signatures, see