chore: upgrade to latest bouncycastle - #51
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
…load Introduce a public InvalidCipherException(Throwable) constructor that preserves the cause chain, and deprecate the BouncyCastle-typed constructor which leaked BC into the SDK's public API. Switch the sole internal caller (EncryptionService) to the new overload via a Throwable cast so overload resolution binds to the non-deprecated variant. The deprecated constructor is retained for binary compatibility and scheduled for removal in v5. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PwN3TUtjUNTobcWKt8dZH4
…b.com:evervault/evervault-java into liam/upgrade-bouncycastle-provider-to-jdk18on
This reverts commit 6e1af10.
Why
dependency on the bouncy castle library was stale and due a patch.
How
Migrate from bcprov-jdk15on to bcprov-jdk18on to resolve several vulns.