United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4924188 jarsigner fails to sign entries with non-english characters in their name
JDK-4924188 : jarsigner fails to sign entries with non-english characters in their name

Details
Type:
Bug
Submit Date:
2003-09-17
Status:
Resolved
Updated Date:
2006-01-13
Project Name:
JDK
Resolved Date:
2003-09-27
Component:
security-libs
OS:
generic,windows_xp
Sub-Component:
java.security
CPU:
x86,generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
1.4.2
Fixed Versions:
5.0 (tiger)

Related Reports
Duplicate:
Relates:

Sub Tasks

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
SUGGESTED FIX

Change sun.security.util.ManifestDigester to use UTF8 keys for
its internal HashMap of entries.

###@###.### 2003-09-24
                                     
2003-09-24
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
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
tiger

FIXED IN:
tiger

INTEGRATED IN:
tiger
tiger-b22


                                     
2004-06-14



Hardware and Software, Engineered to Work Together