Signing 3rd party jars is illegal?!...
843802Jul 24 2006 — edited Jul 31 2006I have used many third party jar files within my application, two such jars are jh-2_0_02.jar and activation.jar. These are pre-signed by the third parties involved, so I have created two separate jnlp files, one for each, both of these are then referenced by my main jnlp file.
Most of the other third party jars are unsigned.
I've now signed my application jar file, and all my developed dependent jar files. These are listed in my main jnlp.
The problem is that all the unsigned third party jars prevent the application from running - 'not all jar files are signed the same', so I created a new jnlp file to put all the 'unsigned' jar files in that.
Putting all the remainingunsigned 3rd part jars in a separate jnlp did resolved the previous error, but now I have security exceptions at runtime - because they're un-signed.
So, is there any way that I can reference unsigned jars and signed jars from my jnlp file without running into security exceptions? Also, are there any legal issues around modifying third party jars - if I'm forced to sign all non-signed jars?