Time Stamping to Maintain Validity of Certificates

As part of the application submission process, before any Windows*-based applications (.MSI, .EXE, .JAR and .AIR) can be published in the Intel AppUp center, it must be signed by a certificate from a Certificate Authority (CA). This certificate gives your customers additional trust when downloading your app from the Intel AppUp center, letting them know that the app does not contain any malware.   

This certificate expires after one year, and we recommend that you renew it to continue to provide your customers with ease of mind that your app is safe to download. Once it has expired, when your customers attempt to download the app —regardless if it is a Windows 7 or Windows 8 operating system— they  will get the Windows warning message saying that the app comes from an “unknown publisher.”  Please note that this will not compromise the availability of your app, but could raise a concern with your customers and potentially cause them not to download the app because it is from an “unknown publisher”.

Consequently, we strongly suggest that developers Time Stamp their applications, so that the certificate remains valid even after it expires. With a valid certificate, your customer will know that the application that they are downloading is from you, a “Verified Publisher.”

Bottom line: Time Stamping your application is optional but we strongly recommend you to do it.

Before your application can be time stamped, you must first obtain a code signing certificate from a Certificate Authority; please read “How Do I Get a Code Signing Certificate” article for more details. Once you’ve gotten the certificate, you’re ready to sign the binary code and time stamp the application. This can be done with the Intel App Signing Tool. To learn more and download the App Signing Tool you can follow this link.

For Time Stamping doubts feel free to visit the forum and post your question or concern.