Found unsigned entry in resource

Question

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 wouldnt the rest of my programs that have been signed the same way also stop working? — Marc Rasmussen, Jul 29 '13 at 13:29
Examine carefully the output of `jarsigner -verify tcm2012.jar` using a 1.7.0_25+ (ideally) SDK. — Andrew Thompson, Jul 29 '13 at 18:07
See also http://stackoverflow.com/questions/19440841/jre-1-7u45-unable-to-load-an-applet-containing-some-unsigned-entries — Vadzim, Sep 23 '16 at 17:53

score 24 · Accepted Answer · edited Feb 24 '15 at 05:41

24

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!

edited Feb 24 '15 at 05:41

Giacomo1968

25,759
11
71
103

answered May 26 '14 at 16:53

martins.tuga

1,662
1
16
20

Also 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: http://web.archive.org/web/20140301230037/http://blog.atlashost.eu:80/post/found-unsigned-entry-in-resource-java-web-start.html – Attila Csipak Dec 05 '17 at 12:04
Actually, there's a fresher link to the above content: https://nowaker.net/post/found-unsigned-entry-in-resource-java-web-start.html (Looks like the author, Damian Nowak moved his blog to his own domain since 2014.) – Attila Csipak Dec 05 '17 at 17:13

score 10 · Answer 2 · answered Nov 11 '16 at 15:12

10

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.

answered Nov 11 '16 at 15:12

Horcrux7

23,758
21
98
156

I installed "Java SE Runtime Environment 8u74" (jre-8u74-windows-i586.exe) from https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html just as you directed. It solved the above problem. Many thanks, Horcrux7. – Erdogan CEVHER Oct 20 '21 at 21:38

score 2 · Answer 3 · answered Mar 31 '16 at 09:48

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

score 0 · Answer 4 · edited Mar 20 '17 at 10:04

0

I my case the applet really had unsigned entry in META-INF folder. ) One way to fix that would be to re-sign it. But in java 8 self-signed applets were demoted to almost the same level as unsigned ones. And the applet didn't required any additional privileges. So it was sufficient to just un-sign it and add to trusted sites list.

edited Mar 20 '17 at 10:04

Community

1
1

answered Oct 11 '16 at 22:12

Vadzim

24,954
11
143
151

score 0 · Answer 5 · answered Oct 27 '16 at 11:55

I had the same problem when compiling on my linux maschine (with JDK 6 U45). But I got this error only when I also tried to start the signed application with Java 6 U45.

When I try to start the application with a newer Java-Version (e.g Java 8) it was OK all the time, with no error message.

When I used a windows maschine to compile the project (also with 6 Update 45), it strangely works also when I use Java 6 U45 to start.

Just my 2 cents.... Cheers!

Found unsigned entry in resource

5 Answers5

Linked