XPISigner v1.4 released
Version 1.4
- You no longer need to run the program from the directory you want to add to your XPI.
- If a certificate chain was attached to a private key, only the end certificate would be added to the signer info in the XPI. This prevented Firefox from verifying extensions signed with multi-level certificate chains.
Known Issues
Some pfx files generate an Illegal Key size exception even though the JRE has been updated with the Unlimited Strength Policy files. Importing the pfx into IE and re-exporting it seems to fix this issue.
Comment from Billy
Time July 6, 2007 at 10:21 pm
I just installed the 1.4 version, and now I’m getting this error. Any ideas on what to try next?
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.oregan.xpi.Main.getInstance(Unknown Source)
at org.oregan.xpi.Main.doSign(Unknown Source)
at org.oregan.xpi.Main.main(Unknown Source)
Caused by: java.lang.NullPointerException
at java.io.File.(Unknown Source)
at org.oregan.xpi.XPISigner.(Unknown Source)
at org.oregan.xpi.bc.XPISignerImpl.(Unknown Source)
… 7 more
Failed to load XPISigner internal module: Check xpi.jar is intact.