Skip to Main Content

Java SE (Java Platform, Standard Edition)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Adding jnlp.packEnabled to signed JNLP results in verification failure on start

2749078Feb 18 2015 — edited Feb 19 2015

Hi,

according to the last security changes in java we're signing our JNLP by adding a JNLP-Template to our main-jar and sign all jars in our projects.

Now we want to reduce the download-time and added for some jars a pack.gz.

We're normalzing all jars (--repack --segment-limit=-1) and pack them with the same arguments.

This all works fine.

Now we added
<property name="jnlp.packEnabled" value="false" />
to our jnlp and

<property name="jnlp.packEnabled" value="*" />

to our template.

But now we get an error on start that the jnlp does not match the template?!?!
I've compared both - they are equal.

I've I simple remove the property all works as expected (without the pack200-support of course).

I'm using this java-version on Windows 7

java version "1.8.0_31"

Java(TM) SE Runtime Environment (build 1.8.0_31-b13)

Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)

Does anybode have an idea how to get pack200 enabled without the error?

This is the Exception:

JNLPSigningException[Signatur der Startdatei konnte nicht validiert werden. Die signierte Version stimmt nicht mit der heruntergeladenen Version überein.]

  at com.sun.javaws.jnl.LaunchDesc.checkSigningTemplate(Unknown Source)

  at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDescHelper(Unknown Source)

  at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDesc(Unknown Source)

  at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedLaunchDesc(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)

This post has been answered by 2749078 on Feb 19 2015
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 19 2015
Added on Feb 18 2015
1 comment
1,428 views