8307134: Add GTS root CAs

[jerboaa]

Clean backport modulo path changes to match 8u layout. Parity backport for 8u381 Oracle.

Testing:

• sun/security/lib/cacerts/VerifyCACerts.java and security/infra/java/security/cert/CertPathValidator/certification passed.
• GHA

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8307134: Add GTS root CAs

Reviewers

• Andrew John Hughes (@gnu-andrew - Reviewer) ⚠️ Review applies to 8a359dee

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 321

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back sgehwolf! A progress list of the required criteria for merging this PR into pr/320 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 backport pull request has now been updated with issue from the original commit.

[jerboaa]

The one GHA failure is unrelated. Seems a flaky test which occasionally fails on 32bit x86.

[mlbridge]

Webrevs

• 02: Full (9c6d4ff5)
• 01: Full - Incremental (8a359dee)
• 00: Full (8a359dee)

[jerboaa]

The only changes to the 11u version have been to the path to files which are different in 8u. Therefore marking as clean.

/clean

[openjdk]

@jerboaa This backport pull request is now marked as clean

[gnu-andrew]

Confirmed to match openjdk/jdk11u-dev#1892 bar path shuffling. Approved for 8u.

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout jdk-8307134-add-gts-certs
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@jerboaa This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8307134: Add GTS root CAs

Reviewed-by: andrew

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@jerboaa Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[jerboaa]

/integrate

[openjdk]

Going to push as commit 8efa32e.

[openjdk]

@jerboaa Pushed as commit 8efa32e.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.