JDK-8353299 doesn't fix the root cause of the test issue, which is the fact that it is interpreting zip data as UTF-8 to get an index, and then using that index to modify the same data interpreted as bytes.

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 JDK-8353299 comment for further explanation:
https://bugs.openjdk.org/browse/JDK-8353299?focusedId=14817153&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14817153