January 6, 2015
We have an adobe air application which has a code signing certificate included during creation of the package. I added another layer by creating a windows installer(via Inno Setup) then using microsoft signtool to pass on the code signing certificate. I recently tried to download the file via Chrome and the message:
<file> is not commonly downloaded and could be dangerous
was displayed along the lines of the image below:
I did a quick google and found the following message on an adobe forum. The user recommended the DigiCert Certificate Utility which is available here.
I took my exe file and applied the adobe code signing certificate to this windows installer wrapped package using the Certificate Utility. Voila! The error message was no longer occurring when downloading via Chrome.
November 19, 2013
I recently upgraded to a Windows 7 machine and needed to install the signtool on my new pc. This is a followup to the post Installing Microsoft signtool.exe posted in May 2012.
I searched the web for the download location for the Windows 7 version of the SDK and found this url: Windows SDK for Windows 7 and .NET Framework 4.
I downloaded the winsdk_web.exe file and tried to install a minimal version of the SDK since I only wanted the signtool.exe. I was not able to successfully install this version since I did not have the correct .NET version. I was getting the error message “Some components cannot be installed” message.
So instead of upgrading to .NET 4 version I returned to the previous download link and perused the archived versions. I found the download for the Windows SDK .NET Framework 3.5 SP1 archived version which is preinstalled on all Windows 7 machines. I downloaded the new winsdk.exe for this version.
I selected the same settings as I did for Windows XP version:
Windows 7 SDK options Selected
This installation ran smoothly and in a similar manner to the one for windows XP.
I can now access the signtool on my new desktop with a minimal windows SDK installation.
May 8, 2012
I have signtool.exe installed on my desktop pc. I now need to configure the InnoSetup script to incorporate a digital signature during the generation of the installation package executable. The following links were used as resources when configuring the InnoSetup program:
May 8, 2012
I first googled to find a free digital signing tool for a windows program and found a page on the Global Sign website. The Global sign website (which is where I got my digital certificate) had a page discussing GlobalSign Code Signing Tools. Realized I needed to use signtool.exe for a microsoft application.
May 8, 2012
Every have a DOH moment?
So I have created an air application that can be deployed on the desktop, mobile devices and the web. For each version, I followed the directions to package the application using digital certificates in Flashbuilder 4.6 for a signed application with a captive runtime.
Note: The mobile device packaging zips all the necessary files and directories and the captive runtimes with a digital certificate into a single file. So the Android pocketnotes.apk file for example will have an associated digital certificate (as does the iphone/ipad pocketnotes.ipa file).
April 24, 2012
Now that we can include the captive runtime for an AIR application when exporting an Adobe Flex project on Windows, I looked into installer software packages that allowed you to wrap the output directory (which in our case included multiple xml files as well as the generated swf file) into an Windows based installation package for the desktop.
I followed the directions at the Adobe site to export a release version of an application using flashbuilder.