Signing Applets

The standard version of SoftArtisans JFile is signed by SoftArtisans, Inc. In the case of a hidden upload or download, it will display a confirmation dialog asking the user if he or she agrees to transfer the file.

With the SoftArtisans signed version of JFile, you also received the unsigned Java classes, allowing you to create an applet with your company signature, that will not display a transfer confirmation dialog.

SoftArtisans, Inc. disavows all responsibility for malicious use of the JFile applet to take files from a user's hard disk or to place files on a user's hard disk without their consent. By signing the applet with your signature, you assume full responsibility that the applet is used in an appropriate manner that respects the user's privacy and integrity.

Step 1: Obtaining a Code Signing Certificate

To sign the applet, you must obtain a Software Developer's Certificate from a Certificate Authority such as Versign. See http://www.verisign.com/developers/ for the latest information about obtaining a Developer's Certificate.

To create a signed applet for use with Netscape Navigator, you must create a JAR file using a Digital ID for Netscape Object Signing.

To create a signed applet for use with Microsoft Internet Explorer, you must create a CAB file using a Digital ID for Microsoft Authenticode.

Step 2: Signing the applet for Netscape Navigator:

If you already have a certificate you must import it into the Netscape browser for the following to work properly.

If you would only like to test the applet you can create a test certificate for Netscape. For more information on how to do this, see http://developer.netscape.com/docs/manuals/signedobj/signtool/index.htm

Creating and Signing a JAR

Step 3: Signing the applet for Microsoft Internet Explorer:

If you already have certificates (.cer and .spc), place them in JFile's \lib\iecert directory.

Creating a Test Certificate for IE

For more information about signing and cabs see Microsoft KB Article Q168941 at http://support.microsoft.com/support/kb/articles/Q168/9/41.asp

Signing the CAB with a timestamp allows the signature on the CAB to stay valid after the certificate has expired. Our sample shows how to sign the CAB using the Verisign timestamp service. The machine you are using for signing must be able to access the Verisign site in order to obtain the timestamp. In our tests, the signcode utility from Microsoft could not access the Verisign site across a proxy server. It requires a direct connection to the Internet.

Creating and Signing a CAB

Step 4: Signing the applet for Macintosh Internet Explorer:

See the following article for instructions on signing the jar file for Mac IE:
http://developer.apple.com/technotes/tn/tn1175.html

Previous Page Next Page