PM64540: SIGNATURE OF SIGNED JAR FILES BROKEN DURING APPLICATION DEPLOYMENT

Fixes are available

APAR status

Closed as program error.

Error description

Product Version: WebSphere Application Server 7.0.0.17

Operating System and Additional Info:

Linux, version 2.6.18-238.1.1.el5
Java version = 1.6.0, Java Compiler = j9jit24, Java VM name =
IBM J9 VM

Problem Description:

Deploy an application with "Use Binary Configuration"
enabled, and change the sequence of class loading after the
deployment.

The MANIFEST.MF of a signed jar in this application will be
modified, which will break the signature of the signed jar.

Run the command "jarsigner -verify" for the jar file, the
following output will be seen:

jarsigner: java.lang.SecurityException: Invalid signature file
digest for Manifest main attributes

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 who have an application         *
*                  containing signed JAR files.                *
****************************************************************
* PROBLEM DESCRIPTION: java.lang.SecurityException: Invalid    *
*                      signature file digest for               *
*                      Manifest main attributes                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The application is not able to access resources in the signed
JAR file because the signature is broken. When you run the
command "jarsigner -verify" for the jar file, the following
output will be seen:
java.lang.SecurityException: Invalid signature file digest for
Manifest main attributes
Each time the application server extracts or saves JAR files
it rewrites the MANIFEST.MF file of the JAR file.  This breaks
the signature of the JAR file.

Problem conclusion

The step to rewrite the MANIFEST.MF file was unnecessary and
has been removed.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.25.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM64540
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-13
Closed date
2012-06-05
Last modified date
2012-06-05

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM64540: SIGNATURE OF SIGNED JAR FILES BROKEN DURING APPLICATION DEPLOYMENT

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?