Comments for Innovative Software Solutions http://blog.ksoftware.net Fri, 02 Dec 2011 03:25:31 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on Exporting your Code Signing Certificate to a PFX File (From FireFox) by Mitchell Vincent http://blog.ksoftware.net/2011/07/exporting-your-code-signing-certificate-to-a-pfx-file-from-firefox/comment-page-1/#comment-5655 Mitchell Vincent Fri, 02 Dec 2011 03:25:31 +0000 http://blog.ksoftware.net/?p=87#comment-5655 Updated with some new screenshots and a tip about the location of the "Options" window if you don't have the "Tools" menu. Updated with some new screenshots and a tip about the location of the “Options” window if you don’t have the “Tools” menu.

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Richard Andresen http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5654 Richard Andresen Wed, 16 Nov 2011 04:03:46 +0000 http://blog.ksoftware.net/?p=142#comment-5654 Hi Mitchell, try a command prompt window with something like this (I'm using Windows 7) "C:\Program Files\kSign\kSignCMD.exe" /f “C:\Users\Richard Andresen\Documents\CodeSigningCert2011_rpa.pfx” /p mypassword /d "5Spice_Install" /du "http://www.5Spice.com/" "C:\Users\Richard Andresen\Documents\FileToSign.exe" error msg: The filename, directory name, or volume label syntax is incorrect notes: Windows 7 seems to accept "Documents" and "My Documents" as equivalent in User path names. I tried both. If the path to the .exe file is incorrect I get a different error msg. Hi Mitchell,
try a command prompt window with something like this (I’m using Windows 7)

“C:\Program Files\kSign\kSignCMD.exe” /f “C:\Users\Richard Andresen\Documents\CodeSigningCert2011_rpa.pfx” /p mypassword /d “5Spice_Install” /du “http://www.5Spice.com/” “C:\Users\Richard Andresen\Documents\FileToSign.exe”

error msg: The filename, directory name, or volume label syntax is incorrect

notes: Windows 7 seems to accept “Documents” and “My Documents” as equivalent in User path names. I tried both. If the path to the .exe file is incorrect I get a different error msg.

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Mitchell Vincent http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5653 Mitchell Vincent Tue, 15 Nov 2011 15:11:15 +0000 http://blog.ksoftware.net/?p=142#comment-5653 Hi Richard - I just tested the kSignCMD with the PFX file in a folder with spaces and it worked well for me. Are you getting some sort of error message? Is it just through Inno, or are you seeing the same problem when you run it manually? Hi Richard – I just tested the kSignCMD with the PFX file in a folder with spaces and it worked well for me. Are you getting some sort of error message? Is it just through Inno, or are you seeing the same problem when you run it manually?

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Richard Andresen http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5652 Richard Andresen Tue, 15 Nov 2011 04:03:50 +0000 http://blog.ksoftware.net/?p=142#comment-5652 1. I find that kSignCMD.exe does not tolerate spaces in the path to the .pfx file, even when file and path are enclosed with quotes. Spaces are OK in the path to the file to be signed when file and path are enclosed in quotes. 2. Further the pfx file and its path must not be enclosed with quotes with Inno Setup 5.4.2 unicode version in Windows 7 32bit. But you must enclose with quotes with Inno Setup 5.4.2 ansi version in Windows XP (even though you can’t actually use spaces or kSign fails)! Weird. 3. I may be confused but it seemed necessary to explicitly set SignedUnInstaller=yes in the Setup section of the Inno install file to get things to run the first time. Then seems I can comment this line out. Anyone know exactly what is happening here? 1. I find that kSignCMD.exe does not tolerate spaces in the path to the .pfx file, even when file and path are enclosed with quotes. Spaces are OK in the path to the file to be signed when file and path are enclosed in quotes.

2. Further the pfx file and its path must not be enclosed with quotes with Inno Setup 5.4.2 unicode version in Windows 7 32bit.
But you must enclose with quotes with Inno Setup 5.4.2 ansi version in Windows XP (even though you can’t actually use spaces or kSign fails)! Weird.

3. I may be confused but it seemed necessary to explicitly set SignedUnInstaller=yes in the Setup section of the Inno install file to get things to run the first time. Then seems I can comment this line out. Anyone know exactly what is happening here?

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Gabriel Zastawnik http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5650 Gabriel Zastawnik Tue, 27 Sep 2011 19:05:20 +0000 http://blog.ksoftware.net/?p=142#comment-5650 Great software and also a great idea to combine your tool with Inno Setup which is one of the most powerfull software for developers. Great duo :) Keep developing your tool! Great software and also a great idea to combine your tool with Inno Setup which is one of the most powerfull software for developers. Great duo :)
Keep developing your tool!

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Jeff Leigh http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5643 Jeff Leigh Thu, 15 Sep 2011 20:41:11 +0000 http://blog.ksoftware.net/?p=142#comment-5643 Wish I new this before I bought a cert from Comodo directly. Now I have to figure out how to auto-sign without the hard way. Our builds run on a schedule automatically (who's going to close all those nag page instances of FF). Wish I new this before I bought a cert from Comodo directly. Now I have to figure out how to auto-sign without the hard way. Our builds run on a schedule automatically (who’s going to close all those nag page instances of FF).

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Mitchell Vincent http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5637 Mitchell Vincent Thu, 25 Aug 2011 14:45:05 +0000 http://blog.ksoftware.net/?p=142#comment-5637 Jeremy : Thanks for that, I'll edit the article to make that more clear. Jeremy : Thanks for that, I’ll edit the article to make that more clear.

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Mitchell Vincent http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5636 Mitchell Vincent Thu, 25 Aug 2011 14:44:34 +0000 http://blog.ksoftware.net/?p=142#comment-5636 Przemek : That should only happen if you're not using a certificate you purchased through us. The utility still works for certificates issued from other CAs but the "nag" is that it brings you back to the website. Drop me an email if you are signing with a certificate you got here and we'll figure out what's going on. If you are using a cert from another CA, still email me and I'll convince you with a generous discount coupon to get one from K Soft! ;-) Przemek : That should only happen if you’re not using a certificate you purchased through us. The utility still works for certificates issued from other CAs but the “nag” is that it brings you back to the website.

Drop me an email if you are signing with a certificate you got here and we’ll figure out what’s going on. If you are using a cert from another CA, still email me and I’ll convince you with a generous discount coupon to get one from K Soft! ;-)

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Jeremy North http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5627 Jeremy North Tue, 16 Aug 2011 01:09:27 +0000 http://blog.ksoftware.net/?p=142#comment-5627 If the path to your certificate doesn't contain spaces, then the quotes should not be added. Signing won't work if there are unnecessary quotes. If the path to your certificate doesn’t contain spaces, then the quotes should not be added. Signing won’t work if there are unnecessary quotes.

]]> Comment on How To Automate Code Signing with InnoSetup (and kSign) by Przemek http://blog.ksoftware.net/2011/07/how-to-automate-code-signing-with-innosetup-and-ksign/comment-page-1/#comment-5600 Przemek Wed, 03 Aug 2011 12:41:02 +0000 http://blog.ksoftware.net/?p=142#comment-5600 Thanks for the guide and the software. Is it possible to disable opening your website everytime kSignCmd.exe is used? It's a bit annoying as the page opens twice whenever I compile setup package. Thanks for the guide and the software. Is it possible to disable opening your website everytime kSignCmd.exe is used? It’s a bit annoying as the page opens twice whenever I compile setup package.

]]>