Code Signing CertificatesSoftware Vendors & Organizations
Secure your applications and add trust to your code
Trust means enhanced sales. Software Vendors and Organizations have the ability to digitally sign and timestamp the software they distribute over the Internet. GlobalSign Code Signing Certificates provide the ability for all developers on all platforms to digitally sign and bind their authenticated publisher identity to the software or executable file they distribute.
The timestamp feature ensures end users that the software or executable file they are running is legitimate and has not been tampered with or altered since being published
EV Code Signing certificates build on the existing benefits of standard Code Signing cerificates to offer stronger levels of assurance that the identity of the publisher is correct and has been verified.
Digitally sign Windows ActiveX controls via Authenticode (32 bit and 64 bit .exe, .ocx, .dll or other) and Kernel software for Windows. Windows 7 compatible.
Digitally sign Adobe AIR applications. AIR only allows digitally signed applications to be run.
Digitally sign JAR applet files so your apps can access client-side resources
Digitally sign Microsoft Office macros and Visual Basic Applications (VBA).
Digitally sign Apple Mac applications. Code signing was introduced by Apple in MacOS 9 onwards.
Digitally sign Mozilla and legacy Netscape Object files.
Most end users understand the danger of running unsigned codes. Unsigned code are vulnerable to insertion of malware and spyware thus being unsafe for the end users. Malware and spyware can bring an internet connected set of computers down in no time. End users are encouraged not to run software or executable files which are unsigned.
With a GlobalSign Code Signing Certificate, digitally signed software or application receives higher trust. The end users do not receive a glaring warning on the potential danger of the software. Instead, the end users receive an advisory on what the software is and who published it.
End users are then asked for a decision on whether or not to run the file, and they most of the time run the file seeing it is from a trusted source.
The difference between security warnings that sound alarming and security warnings that are simply advisory in nature give the end users a totally different experience, as in the examples below:
Add an essential level of trust to the application installation process.
The solution is simple. Sign your code!