This is an automated email from the ASF dual-hosted git repository.
lhotari pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 6a78db39bc0 Remove TLS/JSSE statement in BouncyCastle intro (#974)
6a78db39bc0 is described below
commit 6a78db39bc015df71f2b7a522109994f312bfe1a
Author: Yuwei Sung <[email protected]>
AuthorDate: Mon May 4 04:02:39 2026 -0500
Remove TLS/JSSE statement in BouncyCastle intro (#974)
---
docs/security-bouncy-castle.md | 2 +-
versioned_docs/version-4.0.x/security-bouncy-castle.md | 2 +-
versioned_docs/version-4.2.x/security-bouncy-castle.md | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/security-bouncy-castle.md b/docs/security-bouncy-castle.md
index fd645111ad8..6e3e5f70d1f 100644
--- a/docs/security-bouncy-castle.md
+++ b/docs/security-bouncy-castle.md
@@ -16,7 +16,7 @@ In Pulsar, security and crypto have dependencies on
BouncyCastle Jars. For the d
`Bouncy Castle` provides both
[FIPS](https://www.bouncycastle.org/fips_faq.html) and non-FIPS versions. But
in a JVM, you can not include both of the 2 versions, and you need to exclude
the current version before including the other.
-In Pulsar, the security and crypto methods also depend on `Bouncy Castle`,
especially in [mTLS authentication](security-tls-authentication.md) and
[Transport Encryption](security-encryption.md). This document contains the
configuration between BouncyCastle FIPS(BC-FIPS) and non-FIPS(BC-non-FIPS)
version while using Pulsar.
+In Pulsar, the security and crypto methods of end to end encryption also
depend on the Bouncy Castle library. This document contains the configuration
between BouncyCastle FIPS (BC-FIPS) and non-FIPS (BC-non-FIPS) version while
using Pulsar.
## How BouncyCastle modules packaged in Pulsar
diff --git a/versioned_docs/version-4.0.x/security-bouncy-castle.md
b/versioned_docs/version-4.0.x/security-bouncy-castle.md
index fd645111ad8..6e3e5f70d1f 100644
--- a/versioned_docs/version-4.0.x/security-bouncy-castle.md
+++ b/versioned_docs/version-4.0.x/security-bouncy-castle.md
@@ -16,7 +16,7 @@ In Pulsar, security and crypto have dependencies on
BouncyCastle Jars. For the d
`Bouncy Castle` provides both
[FIPS](https://www.bouncycastle.org/fips_faq.html) and non-FIPS versions. But
in a JVM, you can not include both of the 2 versions, and you need to exclude
the current version before including the other.
-In Pulsar, the security and crypto methods also depend on `Bouncy Castle`,
especially in [mTLS authentication](security-tls-authentication.md) and
[Transport Encryption](security-encryption.md). This document contains the
configuration between BouncyCastle FIPS(BC-FIPS) and non-FIPS(BC-non-FIPS)
version while using Pulsar.
+In Pulsar, the security and crypto methods of end to end encryption also
depend on the Bouncy Castle library. This document contains the configuration
between BouncyCastle FIPS (BC-FIPS) and non-FIPS (BC-non-FIPS) version while
using Pulsar.
## How BouncyCastle modules packaged in Pulsar
diff --git a/versioned_docs/version-4.2.x/security-bouncy-castle.md
b/versioned_docs/version-4.2.x/security-bouncy-castle.md
index fd645111ad8..6e3e5f70d1f 100644
--- a/versioned_docs/version-4.2.x/security-bouncy-castle.md
+++ b/versioned_docs/version-4.2.x/security-bouncy-castle.md
@@ -16,7 +16,7 @@ In Pulsar, security and crypto have dependencies on
BouncyCastle Jars. For the d
`Bouncy Castle` provides both
[FIPS](https://www.bouncycastle.org/fips_faq.html) and non-FIPS versions. But
in a JVM, you can not include both of the 2 versions, and you need to exclude
the current version before including the other.
-In Pulsar, the security and crypto methods also depend on `Bouncy Castle`,
especially in [mTLS authentication](security-tls-authentication.md) and
[Transport Encryption](security-encryption.md). This document contains the
configuration between BouncyCastle FIPS(BC-FIPS) and non-FIPS(BC-non-FIPS)
version while using Pulsar.
+In Pulsar, the security and crypto methods of end to end encryption also
depend on the Bouncy Castle library. This document contains the configuration
between BouncyCastle FIPS (BC-FIPS) and non-FIPS (BC-non-FIPS) version while
using Pulsar.
## How BouncyCastle modules packaged in Pulsar
