8321156: Improve the handling of invalid UTF-8 byte sequences for ZipInputStream::getNextEntry and ZipFile::getComment

[rm-gh-8]

Backporting JDK-8321156: Improve the handling of invalid UTF-8 byte sequences for ZipInputStream::getNextEntry and ZipFile::getComment.

Fixes invalid UTF-8 byte sequence handling in:

• ZIP entry names within LOC file headers
• ZIP file comments accessed through ZipFile::getComment

Behavior change: ZipFile::getComment now returns null when invalid UTF-8 sequences are detected during byte-to-String conversion.

Ran GHA Sanity Checks (passed) and related test (passed).

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8321156 needs maintainer approval
• Change requires CSR request JDK-8372026 to be approved

Issues

• JDK-8321156: Improve the handling of invalid UTF-8 byte sequences for ZipInputStream::getNextEntry and ZipFile::getComment (Bug - P4)
• JDK-8372026: Improve the handling of invalid UTF-8 byte sequences for ZipInputStream::getNextEntry and ZipFile::getComment (CSR)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/2480/head:pull/2480
$ git checkout pull/2480

Update a local copy of the PR:
$ git checkout pull/2480
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/2480/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2480

View PR using the GUI difftool:
$ git pr show -t 2480

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/2480.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back rm-gh-8! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

At least one of the issues associated with this backport has a resolved CSR for a different version. As this means that this backport may also need a CSR, the csr label is being added to this pull request to signal this potential requirement. The command /csr unneeded can be used to remove the label in case a CSR is not needed.

[mlbridge]

Webrevs

• 01: Full - Incremental (ffd81272)
• 00: Full (ff176bf6)