GUACAMOLE-1956: Update BouncyCastle PKIX FIPS to latest compatible (v2.1.9).

This commit is contained in:
Michael Jumper
2025-03-04 02:26:49 -08:00
parent 51afe5ade8
commit bcdb62fbe7
9 changed files with 33 additions and 11 deletions

View File

@@ -1 +0,0 @@
org.bouncycastle:bcutil-fips:jar:2.0.3

View File

@@ -1 +0,0 @@
org.bouncycastle:bcpkix-fips:jar:2.0.7

View File

@@ -1,7 +1,7 @@
BouncyCastle PKIX APIs, FIPS Distribution (https://www.bouncycastle.org/fips-java)
-----------------------------------------------------------------------
Version: 2.0.7
Version: 2.1.9
From: 'The Legion of Bouncy Castle' (https://www.bouncycastle.org)
License(s):
MIT (bundled/bouncycastle-pkix-fips-2.0.7/LICENSE)
MIT (bundled/bouncycastle-pkix-fips-2.1.9/LICENSE)

View File

@@ -0,0 +1 @@
org.bouncycastle:bcpkix-fips:jar:2.1.9

View File

@@ -1,7 +1,7 @@
Bouncy Castle ASN.1 Extension and Utility APIs (https://www.bouncycastle.org/fips-java)
-----------------------------------------------------------------------
Version: 2.0.3
Version: 2.1.4
From: 'The Legion of Bouncy Castle' (https://www.bouncycastle.org)
License(s):
MIT (bundled/bouncycastle-fips-2.0.3/LICENSE)
MIT (bundled/bouncycastle-fips-2.1.4/LICENSE)

View File

@@ -0,0 +1 @@
org.bouncycastle:bcutil-fips:jar:2.1.4

View File

@@ -123,17 +123,32 @@
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-fips</artifactId>
<version>2.0.7</version>
<version>2.1.9</version>
<!-- Force usage of known version of bc-fips, rather than a future
unknown version (bcpkix-fips references bc-fips using a version
range, resulting in newer versions getting pulled in automatically,
breaking the automated license check) -->
<exclusions>
<!--
Force usage of known version of bc-fips, rather than a
future unknown version (bcpkix-fips references bc-fips using
a version range, resulting in newer versions getting pulled
in automatically, breaking the automated license check).
-->
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bc-fips</artifactId>
</exclusion>
<!--
Force usage of known version of bcutil-fips, rather than a
future unknown version (bcpkix-fips references bctuil-fips
using a version range, resulting in newer versions getting
pulled in automatically, breaking the automated license
check).
-->
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bcutil-fips</artifactId>
</exclusion>
</exclusions>
</dependency>
@@ -145,6 +160,13 @@
<version>2.1.0</version>
</dependency>
<!-- Force usage of known version of bcutil-fips (see bcpkix-fips above) -->
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcutil-fips</artifactId>
<version>2.1.4</version>
</dependency>
</dependencies>
</project>