-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b17
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8368317 | 25.0.2 | Francisco Ferrari Bihurriet | P4 | Resolved | Fixed | master |
JDK-8368473 | 21.0.10 | Francisco Ferrari Bihurriet | P4 | Resolved | Fixed | master |
As a result, modifyJarEntryName is modifying some unknown place before the matched entryName, which depends on how many bytes were counted as a single multibyte UTF-8 character.
This issue proposes a fix to modifyJarEntryName, so it operates on bytes, allowing us to re-introduce verifySignatureEntryName.
Please see this
https://bugs.openjdk.org/browse/JDK-8353299?focusedId=14817153&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14817153
- backported by
-
JDK-8368317 VerifyJarEntryName.java: Fix modifyJarEntryName to operate on bytes and re-introduce verifySignatureEntryName
-
- Resolved
-
-
JDK-8368473 VerifyJarEntryName.java: Fix modifyJarEntryName to operate on bytes and re-introduce verifySignatureEntryName
-
- Resolved
-
- relates to
-
JDK-8353299 VerifyJarEntryName.java test fails
-
- Resolved
-
-
JDK-8339280 jarsigner -verify performs cross-checking between CEN and LOC
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk21u-dev/3e41a78d
-
Commit(master) openjdk/jdk25u/c2d79609
-
Commit(master) openjdk/jdk/1b9a1168
-
Review(master) openjdk/jdk8u-dev/699
-
Review(master) openjdk/jdk11u-dev/3098
-
Review(master) openjdk/jdk17u-dev/3954
-
Review(master) openjdk/jdk21u-dev/2235
-
Review(master) openjdk/jdk25u/221
-
Review(master) openjdk/jdk/27319