Skip to content

[deps] upgrade BC to version 1.85#367

Merged
kares merged 1 commit into
jruby:masterfrom
Sharpie:bouncycastle-185
Jul 20, 2026
Merged

[deps] upgrade BC to version 1.85#367
kares merged 1 commit into
jruby:masterfrom
Sharpie:bouncycastle-185

Conversation

@Sharpie

@Sharpie Sharpie commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

BouncyCastle 1.85 was tagged at the beginning of the week. As of today, Friday July 17th, the release notes have not been published to the website:

https://www.bouncycastle.org/download/bouncy-castle-java/#release-notes

However, the git docs indicate nearly three dozen CVE fixes in this release:

https://github.com/bcgit/bc-java/blob/r1rv85/docs/releasenotes.html#L332-L363

This PR bumps the version included with jruby-openssl to 1.85.

Signed-off-by: Charlie Sharpsteen <charlie@overlookinfratech.com>
@Sharpie

Sharpie commented Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

One item to be aware of: BC 1.85 started enforcing the 64 character limit on certificate CN= fields that is specified by RFC 5280. This makes the new library version unable to manipulate long certificate names that were previously fine.

They did add an example of how to work around the new behavior:

bcgit/bc-java@a6ae246

@kares
kares merged commit a40d9a2 into jruby:master Jul 20, 2026
22 checks passed
@Sharpie
Sharpie deleted the bouncycastle-185 branch July 20, 2026 12:37
@Sharpie

Sharpie commented Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

And a quick follow-up: it looks like the length enforcement in BouncyCastle 1.85 doesn't affect the jruby-openssl implementation of things like OpenSSL::X509::Name because Strings are pre-encoded to DER format and the character limit is only enforced when BouncyCastle processes a String value.

@kares

kares commented Jul 20, 2026

Copy link
Copy Markdown
Member

Thanks, I've run the check with a bunch of external test suites as well and everything seemed 🟢

@headius headius added this to the 0.16.2 milestone Jul 20, 2026
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.

3 participants