Skip to content

Update bcpkix-jdk18on from 1.79 to 1.81#18888

Merged
abhishekrb19 merged 1 commit into
apache:masterfrom
ashwintumma23:bcst
Jan 13, 2026
Merged

Update bcpkix-jdk18on from 1.79 to 1.81#18888
abhishekrb19 merged 1 commit into
apache:masterfrom
ashwintumma23:bcst

Conversation

@ashwintumma23

Copy link
Copy Markdown
Contributor

Description

Summary ...

Updates bcpkix-jdk18on from 1.79 to 1.81 to address SONATYPE-2025-001911.

Reason for upgrade

  • Upgrading bcprov-jdk18on from 1.79 to 1.81 to address security vulnerabilities and improve cryptographic stability.
  • Resolves SONATYPE-2025-001911, which addresses a flaw in the DigestFactory regarding improper SHA-1 cloning.
  • Includes compatibility fixes for Initialization Vector (IV) validation introduced in the 1.80 release cycle.

Tests

  • Verified the dependency resolves correctly
  • Build completes successfully with the updated version

Release note

Upgraded org.bouncycastle:bcpkix-jdk18on version to 1.81 to resolve SONATYPE-2025-001911


Key changed/added classes in this PR
  • Top Level pom.xml

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@abhishekrb19

Copy link
Copy Markdown
Contributor

@kfaraz, some of the recently added embedded tests are failing, wondering if you have any thoughts. I’m pretty sure it’s not related to the change in this PR. I can also help take a look at some of these failures later when I get a chance

  🧪 - KafkaFaultToleranceTest | expected: <3000> but was: <3460>
     🧪 - KafkaFaultToleranceTest | expected: <false> but was: <true>
     🧪 - FaultyClusterTest | Query[SELECT COUNT(*) FROM %s] failed ==> expected: <1000> but was: <500>

@kfaraz

kfaraz commented Jan 8, 2026

Copy link
Copy Markdown
Contributor

Thanks for letting me know, @abhishekrb19 ! I have encountered some of these failures too. Will try to take a look.

@abhishekrb19

Copy link
Copy Markdown
Contributor

Ack, thanks @kfaraz!

@abhishekrb19
abhishekrb19 merged commit 0e1afd7 into apache:master Jan 13, 2026
186 of 191 checks passed
@ashwintumma23
ashwintumma23 deleted the bcst branch January 13, 2026 17:08
@kgyrtkirk kgyrtkirk added this to the 36.0.0 milestone Jan 20, 2026
kgyrtkirk pushed a commit that referenced this pull request Jan 20, 2026
Upgraded org.bouncycastle:bcpkix-jdk18on version to 1.81 to resolve SONATYPE-2025-001911

Co-authored-by: Ashwin Tumma <[email protected]>
(cherry picked from commit 0e1afd7)
santosh-d3vpl3x added a commit to santosh-d3vpl3x/druid that referenced this pull request Feb 5, 2026
bcpkix-jdk18on:1.81 requires bcprov-jdk18on:[1.81,1.82) per its POM.
This was missed in apache#18888 which updated bcpkix but not bcprov,
causing license check failures.
santosh-d3vpl3x added a commit to santosh-d3vpl3x/druid that referenced this pull request Mar 16, 2026
bcpkix-jdk18on:1.81 requires bcprov-jdk18on:[1.81,1.82) per its POM.
This was missed in apache#18888 which updated bcpkix but not bcprov,
causing license check failures.
santosh-d3vpl3x added a commit to santosh-d3vpl3x/druid that referenced this pull request Mar 21, 2026
bcpkix-jdk18on:1.81 requires bcprov-jdk18on:[1.81,1.82) per its POM.
This was missed in apache#18888 which updated bcpkix but not bcprov,
causing license check failures.
FrankChen021 pushed a commit that referenced this pull request Mar 30, 2026
…extension (#18843)

* feat: add Consul discovery contrib extension, harden Consul discovery and leadership election

* feat: add Consul discovery contrib extension, harden Consul discovery and leadership election

* fix: address code review feedback for Consul discovery extension

- Fix leaderSessionTtl computation: track explicit user setting via flag
  to correctly recompute TTL from healthCheckInterval when omitted
- Change leaderMaxErrorRetries default to unlimited (Long.MAX_VALUE) for
  null/0/negative values since giving up breaks cluster operation
- Add null session guard in leader election loop with backoff to prevent
  tight retry loops when session creation fails
- Validate watchSeconds >= 1 second to prevent non-blocking query loops
  caused by Duration.getStandardSeconds() truncation
- Fix metadata size check to use UTF-8 byte length instead of char count
  for correct Consul 512-byte limit enforcement
- Add null check for announcedNodes during re-registration to handle
  concurrent unannouncement during shutdown
- Update docs to reflect unlimited retry default behavior

* fix: update parent version to 37.0.0-SNAPSHOT

* fix: align bcprov-jdk18on version with bcpkix-jdk18on (1.79 -> 1.81)

bcpkix-jdk18on:1.81 requires bcprov-jdk18on:[1.81,1.82) per its POM.
This was missed in #18888 which updated bcpkix but not bcprov,
causing license check failures.

* test: restore incremental cache config for consul docker tests

* style: remove trailing whitespace in consul changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants