Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IllegalArgumentException in OcspCache when optional parent revocation checker OcspExtensions is empty #1548

Closed
felixdo opened this issue Dec 11, 2023 · 9 comments
Assignees

Comments

@felixdo
Copy link

felixdo commented Dec 11, 2023

This is probably happening since 1.77 caused by the fix for 1479. The OcspCache should somehow check that it doesnt create Extensions from an empty list, which is afaiu the default in PKIXRevocationChecker.

@dghgit
Copy link
Contributor

dghgit commented Jan 5, 2024

This is fixed in the latest beta at https://www.bouncycastle.org/betas

@felixdo
Copy link
Author

felixdo commented Jan 8, 2024

@dghgit Are the betas somehow consumable by maven/gradle builds?

@dghgit
Copy link
Contributor

dghgit commented Jan 9, 2024

If you rename the jars to end with 178-SNAPSHOT.jar instead of 178b*.jar you should find the tools can use them okay.

@adodao
Copy link

adodao commented Jan 14, 2024

When is version 1.78 planned to be released with the fix? When validating the SwissSign certificates via this OCSP (
http://ocsp.swisssign.ch) returns this exception.

-> basicOCSPResp.getResponses();

@dghgit dghgit self-assigned this Feb 12, 2024
@dghgit
Copy link
Contributor

dghgit commented Feb 12, 2024

The beta builds at https://www.bouncycastle.org/betas are now being distributed in a more "maven friendly" fashion (they end with 1.78-SNAPSHOT, they can also be built directly using ./gradlew clean build in the bc-java repo).

@phaus
Copy link

phaus commented Apr 16, 2024

Good day! is there any update when we could have this fix in a stable release?

@wkruse
Copy link

wkruse commented Apr 16, 2024

It looks like there is already a 1.78 in Maven, but according to the

it shouldn't be used, but 1.78.1 seems to be just around the corner.

@dghgit
Copy link
Contributor

dghgit commented Apr 16, 2024

1.78 is largely safe to use, if you're affected by the issues we're fixing it simply won't work... (so there's no risk of harm, other than inactivity...)

@dghgit
Copy link
Contributor

dghgit commented Apr 22, 2024

Fixed in 1.78.

@dghgit dghgit closed this as completed Apr 22, 2024
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

No branches or pull requests

5 participants