FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Fix OCSP Tests (#17114) by chrisvest · Pull Request #17115 · netty/netty · GitHub

/ netty Public

Fix OCSP Tests (#17114) - #17115

Closed
chrisvest wants to merge 1 commit into
netty:4.1from
chrisvest:4.1-ocsp-fix
Closed

chrisvest wants to merge 1 commit into
netty:4.1from
chrisvest:4.1-ocsp-fix

Conversation

Copy link
Copy Markdown
Member

Motivation:
Google Trust Services, which supply the SSL certificate for netty.io, recently stopped adding OCSP entries to the certificates they create.

This broke some of our OCSP tests, which were relying on reaching out to netty.io and checking the certificate.

Modification:
Change the test domain to instead use apple.com, which still adds OCSP entries to their certificates.

Result:
This makes the tests pass again as a temporary measure. The real fix is to add OCSP support to our netty-pkitesting module, and instead rely entirely on local connections with certificates fully controlled by the test setup.

(cherry picked from commit 7aa3f1f)

Motivation:
Google Trust Services, which supply the SSL certificate for `netty.io`,
recently stopped adding OCSP entries to the certificates they create.

This broke some of our OCSP tests, which were relying on reaching out to
netty.io and checking the certificate.

Modification:
Change the test domain to instead use `apple.com`, which still adds OCSP
entries to their certificates.

Result:
This makes the tests pass again as a temporary measure. The real fix is
to add OCSP support to our netty-pkitesting module, and instead rely
entirely on local connections with certificates fully controlled by the
test setup.

(cherry picked from commit 7aa3f1f)
chrisvest added this to the 4.1.137.Final milestone Jul 21, 2026
chrisvest enabled auto-merge (squash) July 21, 2026 21:23
chrisvest mentioned this pull request Jul 21, 2026

Copy link
Copy Markdown
Member Author

@hyperxpro Can you look into why this is failing? The only difference between this and 4.2 that I can think of, is the BouncyCastle version, but the signature verification (which is where this is failing) delegates to the JDK provider. Maybe TBSResponseData in this version of BouncyCastle isn't round-trip encoding safe and create a different binary encoding which fails the signature check.

Copy link
Copy Markdown
Contributor

@hyperxpro Can you look into why this is failing? The only difference between this and 4.2 that I can think of, is the BouncyCastle version, but the signature verification (which is where this is failing) delegates to the JDK provider. Maybe TBSResponseData in this version of BouncyCastle isn't round-trip encoding safe and create a different binary encoding which fails the signature check.

I'll take a look tomorrow for sure.

Copy link
Copy Markdown
Contributor

Found: #16119

We need this on 4.1 branch. Is it fine if I make the PR?

Copy link
Copy Markdown
Member Author

Found: #16119

We need this on 4.1 branch. Is it fine if I make the PR?

Oh! Yeah, looks like we didn't backport that change. Yes, please make a PR. You can make a combined PR with both backports.

Copy link
Copy Markdown
Contributor

Ack - I will take care then :)

Copy link
Copy Markdown
Member Author

Addressed in #17134

chrisvest closed this Jul 24, 2026
auto-merge was automatically disabled July 24, 2026 17:06

Pull request was closed

chrisvest deleted the 4.1-ocsp-fix branch July 24, 2026 17:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL