JDK-4924188 : jarsigner fails to sign entries with non-english characters in their name
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 1.4.2
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2003-09-17
  • Updated: 2006-01-13
  • Resolved: 2003-09-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Duplicate :  
Relates :  
Description
The attached jar file russian.jar contains entries with russian characters.
When you apply jarsigner from java 1.4.1 all entries are signed.
When you use jarsigner from 1.4.2, the entries with non-english characters remain unsigned.
Same thing happen with german a-umlot, french e-grave, and spanish n-yea 

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b22
2004-06-14

EVALUATION ###@###.### 2003-09-19 Comparing the signed jar generated by 1.4.1 fcs and 1.4.2 fcs using russian.jar, it seems that as a result, only New/AppletClassLoadingBug.class is signed. Need to look into why other jar entries aren't shown up in the *.SF file. However, 1.4.x releases all do it this way; so no change of behavior there.
2004-06-11

SUGGESTED FIX Change sun.security.util.ManifestDigester to use UTF8 keys for its internal HashMap of entries. ###@###.### 2003-09-24
2003-09-24