Signing jars on japplets

[rogene]

Hi there,

Could someone give me the simple low-down on how jars need to be signed/security managed etc to run an applet?

I modified the worldwind basic demo code into a JApplet, but obtain runtime errors. From earlier posts I gather that I need to package my applet as a jar and sign the jar.

Despite a decade of experience with java, this is my first time working with security on jars.

Thanks!

[Chade]

Tried the Java forums yet (slow though they are)?

[rogene]

Thank you - this would be a much more appropriate place to ask my questions. Cheers!

[patmurris]

There are many pages out there discribing the process. A lot are 'old' but are still valid.
It boils down to creating a certificate with keytool once, and signing your jar with it, using jarsigner, each time you rebuild your archive.

http://java.sun.com/j2se/1.4.2/docs/...a_signing.html

[rogene]

The procedure seems straightforward enough, but I am left with the question as to why it is required. Would it be correct to assume that anytime an applet imports classes from a signed jar, that it must itself be signed? Thanks!

[pred]

It must because your main applet launch code such as preparing client DataFileCache ( write access on client required), calling remote URL ( url access on port 80 required ) and I trust that's all. Furthermore, JOGL need to be signed to install ( write acess on client required ) natives drivers, but you can still use JNLP launcher.

Don't forget, Java doesn't transmit explicitely rights access to non initial threads son ( all thread created after applet init ), you need to give them all permission separately.