Tag Archives: Self-signed certificateSelf-signed certificate

TURKTRUST Unauthorized CA Certificates

January 4, 2013 by Bruce Morton     No Comments

Although unrelated to Entrust, I thought you might be interested in the news about TURKTRUST.

Adobe Code-Signing Certificate Compromised

October 3, 2012 by Bruce Morton     No Comments

Adobe announced they received two malicious utilities signed by a valid Adobe code-signing certificate. The code-signing certificate was compromised though an attack on their code-signing system. The code-signing certificate will be revoked on October 4, 2012, and will impact all code being signed after July 12, 2012. A supporting security advisory has been issued. The [Read More...]

Code Signing: Best Practices

July 27, 2012 by Bruce Morton     1 Comment

The biggest issue with code signing is the protection of the private signing key associated with the code signing certificate. If the key gets compromised, then your certificate is worthless. A compromised key may also jeopardizethe software that you have already signed. Here are some best practices for code signing: 1. Minimize access to private [Read More...]

Self-Signed Versus Trusted CA Certificates

July 23, 2012 by Bruce Morton     No Comments

In most cases you have to sign your code in order to get it installed on the operating system. You can sign your code using a self-signed certificate or using a certificate issued by a publicly-trusted CA. Due to the costs of buying a code signing certificate from a publicly-trusted CA, some users will decide [Read More...]

Code Installation Trust Decision

June 21, 2012 by Bruce Morton     No Comments

The code has been signed, the user has started installation, and verification has taken place. How does the user know whether or not to accept the code? Here is a typical code verification security warning: The user must make their trust decision based on the above. The statement provides the following: File Name: In this [Read More...]