-
Bug
-
Resolution: Fixed
-
P1
-
7
-
b141
-
generic
-
generic
-
Verified
We just noticed the bugster webstart application failed to launch with JRE 7 b140. It's failing with exception related to signed jar and certificates:
com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: http://bugster.central.sun.com/bugster/bugster.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$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
We don't think it's a problem in webstart - because we tried with our b140 pit and cannot reproduce the problem. Problem only start to occur when we use rt.jar from promoted b140.
We noticed a few of security/certificate related fixes that got integrated in b140, can your team please help and see if any of the changes might cause the issue ?
com.sun.deploy.net.JARSigningException: Found unsigned entry in resource: http://bugster.central.sun.com/bugster/bugster.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$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
We don't think it's a problem in webstart - because we tried with our b140 pit and cannot reproduce the problem. Problem only start to occur when we use rt.jar from promoted b140.
We noticed a few of security/certificate related fixes that got integrated in b140, can your team please help and see if any of the changes might cause the issue ?
- relates to
-
JDK-7037201 regression: invalid signed jar file not detected
-
- Closed
-