NoSuchAlgorithmException: Signature not avaiable
Hello,
I have inherited a jar signing process from a co-worker who left. No documentation so I don't know what I'm doing wrong. I'm at dead end and hoping someone can help.
I execute the following command:
<path to java/bin>.jarsigner -keystore <path to verisign certificate keystore> -storepass <password> <path to unsigned jar file> <alias>
I'm getting the following error message:
"jarsigner error: java.security.NoSuchAlgorighmException: Signature not available"
Does anyone have any ideas of what could be causing this. ANY help would be greatly appreciated.
Thanks!
[662 byte] By [
pantichd] at [2007-9-30 7:52:46]
Can you see if your <alias> is in the keystore and still valid?
keytool -list -keystore <keystore>
Can you sign a jar using the keytool and jarsigner?
Batch file to sign the applet: (please note this will
delete some files)
del *.cer
del *.com
del *.jar
del *.class
javac -classpath ".;C:\Program Files\Java\j2re1.4.2_04\lib\plugin.jar" test.java
keytool -genkey -keystore harm.com -keyalg rsa -dname "CN=Harm Meijer, OU=Technology, O=org, L=Amsterdam, ST=, C=NL" -alias harm -validity 3600 -keypass pass -storepass pass
jar cf0 test.jar test.class
jarsigner -keystore harm.com -storepass pass -keypass pass -signedjar sTest.jar test.jar harm
del *.class
Well, it turns out that the jarsigning HAS to be done with 1.3.x of jdk. I had been told that the person who left was doing the jarsigning on the WebSphere app server which is running 1.2.x
I downloaded the 1.3.x jdk to my pc, copied the keystore to my pc, and ran the jarsigner with no problem.
Copied the signed file back to WebSphere and restarted VM. Everything works great!
