Found unsigned entry in resource
Solution 1
This worked for me:
Go the Control Panel/Java.
Then click on “Settings” button and activate the option “Keep temporary files on my computer.”
It’s weird, but it worked!
Solution 2
The problem can also occur with older Java Versions if you sign with a newer Java versions.
- Sign with 1.8u74 and older works with all versions
- Sign with 1.8u101 and newer works with 1.7u80 and newer but not with older versions on the client.
There seems a incompatible change in the sign algorithm.
Solution 3
I had a similar problem with my applications.
I' ve a java swing application deployed with javaws:
- when I run the application using JRE 1.6 I get the exception
- when I run the application using JRE 1.7 and JRE 1.8 it works
I checked all the jar, MANIFEST.MF etc. and all was fine. Finally I discovered that I've used a new TSA endpoint to sign my jars.
- when I use this TSA http://tsa.starfieldtech.com the application run fine with JRE6,8
- when I use this TSA http://services.globaltrustfinder.com/adss/tsa the application runs only with JRE8
From this resource http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jarsigner.html I read To generate the time stamp, jarsigner communicates with the TSA with the Time-Stamp Protocol (TSP) defined in RFC 3161. When successful, the time stamp token returned by the TSA is stored with the signature in the signature block file.
Someone can give more insight about this problem? In particular I don't want to be forced to use a particular TSA. Why there are this differences between TSA? Thanks
Related videos on Youtube
Comments
-
Marc Rasmussen over 3 years
i have the following JNLP file:
<jnlp spec="1.0+" codebase="http://****:****" href="tcm2012.jnlp"> <information> <title>TCM 2012</title> <vendor>Drift og Performance, *** Servicecenter</vendor> <homepage href="http://******"/> <description/> </information> <security> <all-permissions/> </security> <resources> <j2se version="1.6+"/> <jar href="tcm2012.jar"/> </resources> <application-desc main-class="com.****.kundeservice.TCMApplication"/> </jnlp>
Now when i try to run in from the web i get the following error:
Found unsigned entry in resource
With the following exepction
com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: http://*****:****/tcm2012.jar at com.sun.javaws.security.SigningInfo.getCommonCodeSignersForJar(Unknown Source) at com.sun.javaws.security.SigningInfo.check(Unknown Source) at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResourcesHelper(Unknown Source) at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResources(Unknown Source) at com.sun.javaws.Launcher.prepareResources(Unknown Source) at com.sun.javaws.Launcher.prepareAllResources(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source) at com.sun.javaws.Launcher.launch(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main.access$000(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
Does anyone know how to fix this problem?
-
Makky almost 11 yearsYou need your jars to be signed for JNLP.
-
Marc Rasmussen almost 11 years@Makky My jar is signed
-
Makky almost 11 yearsok ..are they still valid though?
-
Marc Rasmussen almost 11 yearsThey should be the program worked a few weeks ago
-
Makky almost 11 yearsWhat if their validity was valid until yesterday?
-
Marc Rasmussen almost 11 years@Makky wouldnt the rest of my programs that have been signed the same way also stop working?
-
Makky almost 11 yearsYes. It would stop working.
-
Makky almost 11 yearsThis also check all the depedant jars as well .
-
Andrew Thompson almost 11 yearsExamine carefully the output of
jarsigner -verify tcm2012.jar
using a 1.7.0_25+ (ideally) SDK. -
Vadzim almost 8 years
-
-
Attila Csipak over 6 yearsAlso it's worth to examine the MANIFEST.MF of the (unsigned) jar mentioned in the JarSigningException. This phenomenon seems to be related to package version information entries (e.g. Name: com.package.foo) present in the manifest of the unsigned jar. See also: web.archive.org/web/20140301230037/http://blog.atlashost.eu:80/…
-
Attila Csipak over 6 yearsActually, there's a fresher link to the above content: nowaker.net/post/… (Looks like the author, Damian Nowak moved his blog to his own domain since 2014.)
-
Erdogan CEVHER over 2 yearsI installed "Java SE Runtime Environment 8u74" (jre-8u74-windows-i586.exe) from oracle.com/java/technologies/javase/… just as you directed. It solved the above problem. Many thanks, Horcrux7.