Oh my you are looking at something expensive I think. I read the thread looking for an answer and when it was not there I did a quick search. For your reading pleasure. Will watch the tread to see if you find a reasonable solution.
To be honest, I don't get it. If they are YOUR software, you coded them yourself. If you can code software, the DS is the easiest. For me, you just said: I built a complete car from scratch. Does anybody know how I can change the oil !! Or, there's something I missed...that's why I don't get it I guess....
The software was coded by another company, I just want to add a digital signature to it. Simple enough?
He probably purchased the software and rights to the software right checksum? (otherwise, we cannot help you here)
But...even...I always thought that DS are used to create a PKI, which need to be inserted before compilation... My mistake I guess...
I have access to the .cab package so I can reprogram the software as needed. The more I read the more unneccesary a digital signature sounds.
It really depends on to whom it will be marketed. I don't worry to much when I get that unsigned software message. The average user might panic when that "unsigned" windows message pops up on the screen. If this product is for experienced users it might be a waste of your time and money.
My todo list includes getting a digital signature for some software we sell. In theory we agree that it's a great idea. Practically we're not so enthused. Search for "verified publisher" and you get links like this: http://www.terryscomputertips.com/computers/publisher-could-not-be-verified.php and we take some comfort that Lavasoft aren't signed: Why Isn't Lavasoft From A Verified Publisher?, Afraid To Trust This Download! Our software is written in Visual Foxpro so it's interesting that http://www.google.co.nz/search?q="verified+publisher"+vfp comes up blank although http://www.google.co.nz/search?q="digital+signature"+vfp is more helpful.