HTML Executable v3.6 - Exe from unknown publisher

Hello,

Introduction: We have a paid license to HTML Executable v3.6 and have been using the application over the last few years. We use the Symantec Endpoint protection which has now started detecting all EXE as coming from an unknown publisher/ lacking a proper verified digital signature and the EXE download is getting blocked/ file is deleted as per corporate security guidelines. Therefore, we’re not able to use the EXEs generated by the tool due to this issue. I’m attaching the screenshot for your reference.

Steps we’ve taken: We’ve gone through code signing help doc (http://www.htmlexe.com/help/codesigning). We’ll purchase a valid code signing certificate from K Software but we’ve few queries.

  1. How we will get PFX file, Associated Password & Timestamp URL on above purchase to digitally sign publication ?

  2. What are the next steps after purchasing it ?

  3. After doing all steps, will it sign Exe on the fly & we’ll not get attached pop up on creation & opening the exe ?

Please also suggest any workaround so that we can continue work until we complete digital signing.

Regards,

Sandeep Kumar

  1. The reseller of the code signing certificate will give you instructions about how to create a PFX file. Timestamp URL is explained at http://www.htmlexe.com/help/codesigning

  2. You follow instructions of the reseller for getting your certificate. Your company information must first be checked by Comodo, so it can take a few days.

  3. If you follow steps from http://www.htmlexe.com/help/codesigning, you’ll get a signed EXE file and no more the “publisher could not be verified” warning.

There is no workaround, since it’s a security matter (and a protection for your end users implemented in Windows).

Thanks. We’re creating EXE from our Web application made in Java. After purchasing Code Signing Certificate & getting PFX, associated password how we’ll sign Exe on fly while creating it from Java Code. Can you please guide on this ? Any link or java code excerpt will help.

HTMLEXE handles code signing itself when building the publication EXE; just configure the project as explained in the doc.