I've been trying to understand the various options for getting my applet signed and I
wondered if someone can help out. The applet is currently being used on an intranet
and the java.policy has to be manually edited to grant certain permissions (not least
showWindowWithoutWarningBanner), I want to remove this step as far as possible.
>From what I've learned so far..
1) If using IE the .class files have to be inserted into a cab file (rather than a
jar) and then this is signed, paying $400 from Verisign (or $200 from Thawte?)
2) As the applet is being used on a intranet does it have to be signed by Verisign or
such like or can I sign it so it works but says its from an Untrusted Source?
3) Thawte claim to be able to do signing for both Netscape and IE but then talks about
using 1.3 for this, does this mean I would need the 1.3 plugin from Sun (rather than
the 1.2.2 that I'm using)
Ideally I would like it to be signed for both Netscape and Explorer but as Javascript
can be used to select the correct cab/jar file this isn't a necessity.
Any help with anyone who has got experience in this area who can help/confirm/refute
anything I've written would be appreciated.
The whole area seems complicated and I don't want to buy a certificate and it turning
out to be not what I need!
Rob
--
Rob Kirkbride
Syseca
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
