This is an automated email from the ASF dual-hosted git repository.
hepin pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-pekko.git
The following commit(s) were added to refs/heads/main by this push:
new 6a5e75661d no need to mention old Akka version behaviours relating to
TLS auth
6a5e75661d is described below
commit 6a5e75661d90f2dc502658666939db94be8096ff
Author: PJ Fanning <[email protected]>
AuthorDate: Fri Feb 17 13:27:24 2023 +0100
no need to mention old Akka version behaviours relating to TLS auth
---
docs/src/main/paradox/remoting.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/src/main/paradox/remoting.md
b/docs/src/main/paradox/remoting.md
index afb7dfc74a..827f6f3eed 100644
--- a/docs/src/main/paradox/remoting.md
+++ b/docs/src/main/paradox/remoting.md
@@ -496,9 +496,9 @@ as well as the [Oracle documentation on creating KeyStore
and TrustStores](https
are both great resources to research when setting up security on the JVM.
Please consult those resources when troubleshooting
and configuring SSL.
-Since Pekko 2.5.0 mutual authentication between TLS peers is enabled by
default.
+Mutual authentication between TLS peers is enabled by default.
-Mutual authentication means that the the passive side (the TLS server side) of
a connection will also request and verify
+Mutual authentication means that the passive side (the TLS server side) of a
connection will also request and verify
a certificate from the connecting peer. Without this mode only the client side
is requesting and verifying certificates.
While Pekko is a peer-to-peer technology, each connection between nodes starts
out from one side (the "client") towards
the other (the "server").
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
