Digital Workshop

Welcome to the Digital Workshop Message Boards
It is currently December 23rd, 2024, 2:25 am

All times are UTC [ DST ]




Post new topic Reply to topic  [ 14 posts ] 
Author Message
 Post subject: Code Signing Exe
PostPosted: October 28th, 2009, 10:47 am 
Offline

Joined: July 12th, 2009, 10:33 am
Posts: 124
Hi

Anyone have any experience code signing a publication file (exe) directly? I usually code sign a setup file which works well. However, I am creating a small, standalone file for internet download and don't want any extra steps in the process of using it (i.e. click and open). If I use SignCode.exe, the publication file becomes corrupted and will not open (ILM: Cannot find publication file).

This may be too obscure a problem and I don't want to start editing binaries. Just wondered if anyone had come across this issue. From what I have found on the net, it is likely a problem with the exe rather than the signcode ap.

Cheers
Dan

_________________
V9.6. Windows 10. Testing on PC, Mac, iPad.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: October 28th, 2009, 8:45 pm 
Offline
User avatar

Joined: October 25th, 2004, 10:33 am
Posts: 257
Location: UK
Opus: Pro 8
OS: Windows 7 Professional x64
System: Dell XPS15 i7x4 2.1Ghz 6GB 128GB SSD
You could try code signing your ilmplay.exe file (in Opus' players\win32 directory) and then publishing. I would imagine the fact that the EXE has changed since code signing would invalidate the code, but it'd be worth a try.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: October 28th, 2009, 10:09 pm 
Offline

Joined: July 12th, 2009, 10:33 am
Posts: 124
That was a good call thanks Dave, but it didn't quite get us over the line. The player is signed, but something still gets corrupted on publishing. The output does open now and the file properties suggest that the signature is in place with all details correct. However, it also states that it is not valid, and on downloading, Windows presents this as 'Unknown Publisher'.

Thanks for the idea (any others are welcome). The alternative is that I just create a very simple Setup package that copies the file to a temp directory and runs it.

Cheers
Dan

_________________
V9.6. Windows 10. Testing on PC, Mac, iPad.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: October 29th, 2009, 9:37 am 
Offline
User avatar

Joined: October 25th, 2004, 10:33 am
Posts: 257
Location: UK
Opus: Pro 8
OS: Windows 7 Professional x64
System: Dell XPS15 i7x4 2.1Ghz 6GB 128GB SSD
If you post a link to a code signed EXE (using your original method), I'll see if I can get it to work.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: October 29th, 2009, 11:11 am 
Offline

Joined: July 12th, 2009, 10:33 am
Posts: 124
Cheers Dave

There are 3 versions in the zipped file:

http://www.orbeducation.co.uk/Pub.zip


1. Unsigned.exe
2. Signed.exe (signed afterwards with MS SignCode.exe)
3. Sig Player.exe (player signed before publishing)

Thanks for having a look at this. My other idea wasn't great, as any use of the setup packager resulted in a file that would likely result in the end of civilised society as we know it (according to MS, atleast). We predominantly sell to schools, and teachers are more likely to be able to run an exe than have install rights.

Ta
Dan

PS. I just read my forum signature. Opus V6 has so far worked without issue on Windows 7.

_________________
V9.6. Windows 10. Testing on PC, Mac, iPad.


Top
 Profile Visit website  
 
 Post subject: Code Signing Exe
PostPosted: November 18th, 2009, 6:54 pm 
is there any way you can make that one thread the only thread they may post on?


Top
   
 
 Post subject:
PostPosted: March 9th, 2010, 11:11 pm 
Offline

Joined: May 25th, 2008, 4:57 pm
Posts: 355
Location: Ireland
Opus: Pro 9.75
OS: Windows 10
System: MacBook Pro (Intel 2020)
What is the progress of code signing Opus publications? If someone is doing this on a regular basis can you post a tutorial of what to do and with costs involved.


Thanks.

_________________
Opus Pro 9.75 on MacBookPro (2020 Intel) running Parallels 19 with Windows 10 (x64)


Top
 Profile  
 
 Post subject:
PostPosted: March 10th, 2010, 12:14 am 
Offline

Joined: July 12th, 2009, 10:33 am
Posts: 124
Code signing is difficult to set up and can cost a bit. Be warned :)

Generally, we use a setup packager to create an install file with the Opus files, icons and a few other bits and bobs. This package is then code signed. On one project, I tried to code-sign the opus file directly, but this corrupted the file. Stick with packaging for now.

There are plenty of tutorials online. Generally:

1. Select a packager (we purchased Setup Builder from lindersoft, but have used free ones in the past). The packager must support code-signing.

2. Buy a certificate (can be a nightmare). We use Comodo.

3. Install the certificate and get it working with the packager (can be even more of a nightmare, especially on Vista or later).

I would suggest you go for as long a period as you are comfortable with. If you go for a 12 month solution you have to do it all again in a year.

The following thread gives you an idea about the type of issues you generally come across. We had similar issues with a different packager/certificate combination used previously, so they are common.
http://www.lindersoft.com/forums/showthread.php?t=8279

Someone may want to add other experiences to this, or flesh out the details.

Cheers
Dan

_________________
V9.6. Windows 10. Testing on PC, Mac, iPad.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: March 10th, 2010, 10:20 am 
Offline
User avatar

Joined: October 25th, 2004, 10:33 am
Posts: 257
Location: UK
Opus: Pro 8
OS: Windows 7 Professional x64
System: Dell XPS15 i7x4 2.1Ghz 6GB 128GB SSD
dan1 wrote:
On one project, I tried to code-sign the opus file directly, but this corrupted the file.


Have you tried it with Opus v7? The player should now be a bit more forgiving.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: March 10th, 2010, 11:06 pm 
Offline
Godlike
Godlike
User avatar

Joined: March 21st, 2007, 10:44 am
Posts: 3188
Location: UK
Opus: Evolution
Dave Emberton wrote:
Have you tried it with Opus v7?


Opus 7 publications can be signed and packaged quite easily and run without any of the problems that previous versions experienced.

Mack

_________________
When you have explored all avenues of possibilities, what ever remains, how ever improbable, must be the answer.

Interactive Solutions for Business & Education
Learn Anywhere. Learn Anytime.

www.interaktiv.co.uk
+44 (0) 1395 548057


Top
 Profile Visit website  
 
 Post subject:
PostPosted: March 11th, 2010, 3:58 pm 
Offline

Joined: May 25th, 2008, 4:57 pm
Posts: 355
Location: Ireland
Opus: Pro 9.75
OS: Windows 10
System: MacBook Pro (Intel 2020)
mackavi wrote:
Opus 7 publications can be signed and packaged quite easily and run without any of the problems that previous versions experienced.


Excellent Mack, is the procedure similar to Dan?

So is it a case of purchasing a Code Signing Certificate, I noticed Comodo.com charge $179 per year and GoDaddy.com charge $199 per year. The price comes down if purchased for longer periods.

So assuming I purchase the certificate, and I use my installer/packager software of choice. I use QSetup from Pantaray Software myself, this supports code signing. Sp the code is applied to the Opus produced exe through the installer/packager.

So each time I release an update or rebuild using Opus, I assume I just apply the same certificate to the exe.

Sorry for the questions, this is something I never looked into before, but will need to do soon and just want to know procedure.

Thanks for the replies.


Just checked prices from Lindersoft, great deals there from $79
http://www.lindersoft.com/products_secu ... rvices.htm

_________________
Opus Pro 9.75 on MacBookPro (2020 Intel) running Parallels 19 with Windows 10 (x64)


Top
 Profile  
 
 Post subject:
PostPosted: March 23rd, 2010, 7:22 am 
Offline

Joined: July 12th, 2009, 10:33 am
Posts: 124
If you are just going to sign and zip the opus exe (and this is now OK with V7) then you can use SignCode.exe (you still have to install your certificates first etc).

If you are using a set-up packager, then I think you probably need to sign the package as it is being created rather than the opus file that goes inside. You save all the settings, so you simply run the packager whenever you publish.

Sorry - this process is a bit hazy already.

_________________
V9.6. Windows 10. Testing on PC, Mac, iPad.


Top
 Profile Visit website  
 
 Post subject:
PostPosted: March 24th, 2010, 12:10 am 
Offline

Joined: May 25th, 2008, 4:57 pm
Posts: 355
Location: Ireland
Opus: Pro 9.75
OS: Windows 10
System: MacBook Pro (Intel 2020)
I will be doing this procedure soon and will update on progress.

_________________
Opus Pro 9.75 on MacBookPro (2020 Intel) running Parallels 19 with Windows 10 (x64)


Top
 Profile  
 
 Post subject: Re: Code Signing Exe
PostPosted: April 10th, 2010, 11:41 am 
Offline
Godlike
Godlike

Joined: November 12th, 2005, 1:56 am
Posts: 1474
Location: SFBay Area
Opus: OpusPro v9.0x, & Evol.
OS: Vista32
System: Core 2 duo 2Ghz, RAM 3GB, Nvidia Go 7700 - laptop
Here is another article that outlines pretty clearly the steps for getting a certificate from a CA.
While the beginning of the article focuses on Microsoft dev/projects, the main part is good information.

Step-by-step guide to purchasing a certificate
http://www.jeff.wilcox.name/2010/02/codesigning101/

_________________
_good things come to those who wait(0)_


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 14 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 43 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group