|
Posted by =?Utf-8?B?V3l0emU=?= on March 6, 2008, 6:48 am
If you were Registered and logged in, you could reply and use other advanced thread options
Dear Group,
Hope you can advice me with this! If this is not the right forum, your
advice is also appreciated.
] Background
To avoid that our customers are confronted with the 'unknown publisher'
warnings (there are other valid reason to code sign...), we are using Code
Signing and the related certificate from Verisign.
Recently, I noted that one of the signed .exe's did not function as when it
was unsigned (I'm able to reproduce). In fact, it was a Macromedia Flash in
an .exe file. Unsigned it runs the Flash content perfectly, signed, it does
not run any more. Just the Flash Player windows opens, the content does not
play. The signature verifies OK.
I had a similar experience with some flash content converted to .exe using a
tool called FLAjector. After successful signing, executing the .exe triggers
an "X Flash player not installed" error. Unsigned the .exe runs OK.
] Question
I thought that *any* .exe could be signed, but the above example shows that
in this case - though the signature itself appears OK - the resulting signed
.exe does not work as before.
Any suggestions on how to address this? Is this specific to Flash?
Thanks, Wytze
| 
XML site map