loading image
There is a scheduled maintenance on Friday, March 22nd from 10PM to 12AM UTC. During this
time, there will be limited availability. Thank you for your patience. Close

Thawte® Code Signing Certificate

Add a Layer of Assurance to Your Code and Earn Your Customers' Trust

Is your code secure?

With the advent of online distribution, developing and disseminating functional code is easier than ever. However, such an environment also subjects code and software to potential dangers presented by fraudulent and malicious code. Don't expose your customers to these threats. With a Thawte® Code Signing Certificate, you can protect your customers and provide them with the safe, trustworthy code they deserve.

What is Code Signing Certificate?

A Code Signing Certificate is a set of data that identifies an existing entity. The certificate presents the entity's public cryptographic key, allowing the public user to verify the sender's identity.

Code Signing Certificates frequently use digital signatures to verify the identity of the content's creator, as well as confirming that the content has not been tampered with since it was originally distributed. With the rapid growth of content distribution thanks to the Internet, code signing is absolutely critical for securing the delivery of content to the consumer. Code Signing Certificates with digital signatures allow publishes to sign .exe, .cab, .dll, and .ocx files; Java Applets and MIDlets; Microsoft® Office documents with macros; and Apple desktop applications.

The Distribution Process for Code Signing Certificates:

The primary goal of a Code Signing Certificate is to confirm the public key contained in a certificate is, in fact, the public key belonging to the person or entity to whom the certificate is issued.

The implementation of digital certification involves a signature algorithm (digital signature) for signing the certificate.

  1. The client sends a certification request containing name and public key to a certification authority. As an SSL reseller, sslrenewals.com represents 4 different certification authorities: Symantec, Thawte, GeoTrust, and RapidSSL. For the purposes of this Code Signing Certificate, sslrenewals.com represents Thawte.
  2. Thawte creates a special message per the software publisher’s request, which constitutes most of the data in the certificate. Thawte signs the message with its private key, obtaining a separate signature (sig) in the process. Then Thawte returns the message and the signature to the software publisher. Together, these two parts form the certificate.
  3. The software publisher then sends the certificate to an end user to convey trust in the public key.
  4. The end user verifies the signature sig using the Thawte’s public key. If the signature is verified, he accepts the software publisher's public key.

As with any digital signature, anyone can verify, at any time, that the certificate was signed by Thawte, without access to any secret information. The end user needs only to get a copy a certificate in order to access the certificate authority's public key.

Who needs a Thawte® Code Signing Certificate from sslrenewals.com?

It is absolutely necessary for any publisher intending to distribute code or content over the Internet or corporate networks to use a Code Signing Certificate. Secure customers are happy customers. Code Signing Certificates allow business and software publishers to assure their customers about who produced the content and that it has not been tampered with since it's initial distribution. Newer operating systems and Internet browsers are often set to higher security levels, which often require signed content. Software publishers who do not use a Thawte® Code Signing Certificate simply won't be taken seriously in today's environment.

Obtaining Certification from Thawte and other Certificate Authorities:

To obtain a certificate from Thawte and other certificate authorities represented by sslrenewals.com, a software publisher must meet the criteria for either a commercial or an individual publishing certificate and submit these credentials to either a CA or a local registration authority (LRA). The criteria discussed below have been proposed by Microsoft. Note that standards bodies, such as the World Wide Web Consortium (W3C), are reviewing these criteria and they are subject to change. A description of the overall process of obtaining a certificate for code signing ends this section of the document.

Commercial Certification:

In order to acquire a Commercial software publishing certificate, applicants must meet the following prerequisites:

  • Identification - Applicants must submit their name, address, and other material that proves their identity as corporate representatives. Proof of identify requires either personal presence or registered credentials.
  • The Pledge - Applicants must pledge that they will not distribute software that they know, or should have known, contains viruses or would otherwise harm a user's computer or code.

Individual Certification:

The following prerequisites must be met for an individual requesting software publishing certificate:

  • Identification – Applicants must submit their name, address, and other material that will be checked against an independent consumer database to validate their credentials.
  • The Pledge – Applicants must pledge that they cannot and will not distribute software that they know, or should have known, contains viruses or would otherwise maliciously harm the user’s computer or code.

The value of an individual SPC is in the information it provides to users so they can decide whether or not to download the code. Knowing who authored the code, and that the bits have not been altered from the time the code was signed to the present, is reassuring information. Additionally, a browser could be used to access a publisher's Web pages so the user can obtain detailed information about the signed code, the author, and the certificate authority. After learning about this code and the author, the user might decide to run the code, or all future code, coming from this particular individual.

Additional Information About Thawte® Code Signing Certificates:

  • Thawte does not certify the content of a software publisher's code. Code signing certificates are only used to verify the publisher who signed the content and that the content has not been altered or corrupted.
  • It is of critical importance that you time stamp your code when signing it. Time stamping ensures that signed code will not expire when the code signing certificate expires. Signed code which has been time stamped is valid, even after the code signing certificate has expired. A new certificate is only necessary if you want to sign additional code. If you did not use the time stamping option during the signing, you must re-sign your code whenever the code signing certificate changes due to re-keying or renewal.
  • In order to verify whether or not a file has been time stamped, follow these directions:
    • Windows - Use the SignTool.exe utility included with the Windows SDK to verify the presence of a time stamp in code which has been signed.
  • Software publishers should ensure that their customers have the latest Microsoft roots. For Windows XP, everything is automatic. For older versions of the Windows operating system, it is highly recommended that the latest root update is installed. Good security policy dictates that your root certificate store should have the most current root certificate references from all trusted certification authorities, thereby providing the widest capability to recognize trusted content.

Get in touch with The SSL Renewals about purchasing the secure, reliable Thawte® Code Signing Certificate – today.

The New Warranty Limits

Symantec has recently extended the warranty limits for many SSL products (including Symantec ®, Thawte ® and GeoTrust ® brands) which, in some cases offer a distinct advantage over the competition. Symantec SSL Certificates now include up to $1,500,000 of NetSure ® protection.

New warranty limits for NetSure Certificates are as follows and coverage applies to Certificates issued on or after July 30, 2011. Thawte Code Signing Certificate warranty is $50,000

Read More
Thawte

Buy New or Renew Your Thawte® Code Signing Certificate

Installation Service:

Total Domains:
1
Total Servers:
1
Total .00

Thawte Code Signing Certificate

  • Validation Type: OV
  • Reissue: Unlimited
  • Issuance: 1-3 Days
  • Warranty: $50,000
  • Green Address Bar: No
  • SAN Support: No
  • Vulnerability Assessment: No
  • Seal-in-Search: No
  • Site Seal: N/A
  • Wildcard: No
  • Server Licensing: N/A
  • Malware Scan: No
  • Business Validation Icon Image Business Validated
  • Mobile Friendly Icon Image Mobile Friendly
  • Green Address Bar Image Green Address Bar
Key Features and Benefits of Thawte® Code Signing Certificate
  • Thawte Code Signing is a fully Business Validated Certificate
  • A single certificate for most platforms and applications
  • Increase adoption and distribution of software downloads
  • Makes sure your active content or code can't be tampered with Unlimited signing with a valid code signing certificate
  • Reduce error messages and security warnings
  • Protect users from downloading harmful files.
  • Satisfy more platform requirements than any other code signing provider
  • $50,000 warranty.
  • Now supports Silverlight® 4 applications
  • Round-the-clock 24/7 phone, email and chat support

Product Specifications

Security Level: Protect multiple platform applications & softwares
Issuance Speed 1-3 Days
Validation Type Fully Business Validated Certificate
Browser Compatibility 99% the Latest Web Browsers
Re-issue Unlimited reissues
Warranty $50,000 Warranty

 

Assurance & Authentication

Thawte Code Signing Certificates help guarantee the authenticity and identity of your software during the user downloading process. But, before you can display your company details as the publisher and start building your software's online reputation, Thawte requires your company to complete the organization validation process, which typically takes 1-3 business days. During the validation process, Thawte will check to make sure your company is legally registered, has a verifiable address, and a telephone number to complete a quick call. This process can be completed entirely using online directories or databases and may not require any additional documents. And we're here to help, we'll provide you with an easy-to-read validation guide after purchase and have one of our validation experts reach out to you.

SSL Certificate Renewal

Renew your SSL certificate with us with ease!

At SSLRenewals.com, we provide a lightning-fast SSL renewal process in just a few simple steps. Not to mention, when you renew with us, you get a few additional benefits:

Renew your SSL certificate immediately with just a few short streamlined steps.
Complete your SSL certificate renewal within just minutes (sometimes seconds).
100% money-back guarantee and previous discount price matching.
Instantly roll over remaining days on your old certificate (varies by CA, typically up to 90 days).
You'll never miss another renewal again thanks to our expert help and tools.

Support Options

  • Java Code Signing Certificate InstallationGo Now Support Icon 1
  • Microsoft Authenticode Code Signing Certificate InstallationGo Now Support Icon 2
  • Microsoft® Office VBA Code Signing Certificate InstallationGo Now Support Icon 3
  • Buy Professional SSL InstallationGo Now Support Icon 6

Web, Mobile Browsers, Server and Client OS Compatibilities

Browser
  • Firefox 1+, 2+, 3+
  • Netscape 4+
  • AOL 5+
  • Chrome 3+
  • IE 5+, 6+, 7+, 8+
  • Opera 7+
  • Safari
Web Browsers Icon Image
Server and Client OS
  • Control Panels: Ensim, DotNet Panel, Plesk6+, Hsphere, Helm, and more.
  • Web Servers: Apache, Microsoft IIS 7, IIS6, IBM HTTP, Tomcat, Weblogic, Cobalt.
  • E-Mail Servers: Lotus Dominos, Exchange 2010, 2007, 2003, SmarterMail, etc.
  • Client OS: Mac OS X, Snow Leopard, Windows 7, Vista, Xp, 2000, Linux Client OS.
  • Server OS: Linux, Windows Server 2008, 2003, 2000, UNIX, Solaris, Novell, etc.
  • Proxy Server, Routers & Firewalls: Microsoft ISA 2004, ISA 2006, CISCO, etc.
Mobile Browser
  • Apple Iphone, Ipad Safari
  • Palm / Handspring Blazer 2.0+
  • Microsoft Pocket Internet Explorer
  • Netfront 3.0+
  • Blackberry
  • AT&T
Java
  • Platform includes digitally signed .jar files and Java applications for the desktop and the latest mobile devices.
  • 100% Authorized and Recognized by Java Runtime Environment (JRE).
Microsoft Authenticode
  • Platform includes digitally signed 32- and 64-bit user-mode files such as .exe, .cab, .dll, .ocx, .msi, .xpi and .xap files.
  • Authorizes digitally signed code for Microsoft® Office 2000, Microsoft VBA, Netscape Object Signing, and Marimba Channel Signing.
Apple Mac
  • Platform includes digitally signed Apple desktop applications for multiple device platforms such as iphone, iPod, and iPad Applications.
Microsoft Office and VBA
  • Platform Includes digitally signed Microsoft Office .doc, .xls, and .ppt files, which includes VBA objects, scripts and macros.
  • Authorized for third-party applications using VBA and for Microsoft Office.

Our Awesome Customers

Live Chat