not all jar files are signed

Hi All,

We provide, to our customers, a signed jar file which access a native DLL. One of our customers is creating there own applet jar file that uses the classes in our jar file, thus there is a total of two jar files: ours and theirs. If our client does not sign their applet jar file, a security exception is thrown from our class, in our signed jar file. Must all of the jar files be signed to satisfy the security manager? Is there anyway around this problem, since our customer does not want to have to sign their jar file?

Thanks

Alan

[574 byte] By [alanmgay] at [2007-9-30 3:18:33]
# 1

Ok,

I think I've solve the problem. Around the critical code, in the signed jar file, I used an AccessController:

AccessController.doPrivileged(

new PrivilegedAction()

{

public Object run()

{

System.loadLibrary(JAWT_NAME);

System.loadLibrary(LIB_NAME);

return null; // nothing to return

}

}

);

This seems to do the trick, I no longer need to sign the other jar file! Any comment regarding this solution?

Thanks

Alan

alanmgay at 2007-6-29 13:39:02 > top of Java-index,Security,Signed Applets...