Call us 1-888-266-6361

Chat with us Now | Request a Callback | Email Us

About Product

When customers buy software in a store, the source of that software is obvious. When downloaded over the Internet, that same software is not so easy to trust, making a Software Signing Certificate with Authenticode Signature Technology essential. A Software Signing Certificate with Authenticode Signature Technology can benefit any publisher planning to distribute code or content over the Internet. When distributing code you risk the chance of your product being modified, impersonated and re-hosted by malicious third parties, but a Software Signing Certificate with Authenticode Signature Technology from Comodo can put an end to this risk. Software Signing Certificates with Authenticode Signature Technology informs customers that they can trust the software download by verifying code integrity and company legitimacy.

Code Signing Certificates - Features and Benefits

  • Digitally sign 32-bit or 64-bit Portable Executable (.exe, .ocx, .dll or other) or .cab files
  • Create a trusted sales outlet - Wherever they download from, your customers can be sure they are receiving the genuine software
  • Ensure authenticity - Assures users that they know the publisher of the software
  • Ensure integrity - Verifies that code has not been tampered with since publication
  • Widely supported - Compatible with Microsoft Authenticode, Adobe Air, Java, Microsoft Office, Apple, Mozilla, Silverlight, Windows 8, Windows 7 and Windows XP


  • Adobe AIR Code Sign any Adobe Air application

  • Microsoft Office Code Sign any MS Office Macro or VBA (Visual Basic fo Applications) file

  • Apple Code Sign Apple Mac software for Mac OS9 and OSX

  • Microsoft Authenticode Code Sign any Microsoft format (32 and 64 bit) EXE, DLL. OCX, MSI, CAB.

  • Java Code Sign any JAR applet

  • Mozzila Code Sign any Mozzila Object file

  • Microsoft Silverlight Sign any Microsoft Silverlight application or XAF file

Authenticode and Code Signing Digital ID From Comodo

The process is outlined below

  • Publisher obtains a Code Signing Digital ID from Comodo.
  • Publisher creates code.
  • Using the SIGNCODE.EXE utility, the publisher:
    • Creates a hash of the code, using an algorithm such as MD5 or SHA,
    • Encrypts the hash using his/her private key,
    • Creates a package containing the code, the encrypted hash, and the publisher's certificate.
  • The end user encounters the package.
  • The end user's Microsoft browser examines the publisher's Digital ID. Using the Comodo root Public Key, which is already embedded in Authenticode-enabled applications, the end user browser verifies the authenticity of the Code Signing Digital ID (which is itself signed by the Comodo root Private Key).
  • Using the publisher's public key contained within the publisher's Digital ID, the end user browser decrypts the signed hash.
  • The end user browser runs the code through the same hashing algorithm as the publisher, creating a new hash.
  • The end user browser compares the two hashes. If they are identical, the browser messages that the content has been verified by Comodo, and the end user has confidence that the code was signed by the publisher identified in the Digital ID, and that the code hasn't been altered since it was signed.

The entire process is seamless and transparent to end users, who see only a message that the content was signed by its publisher and verified by Comodo.