From c03da3a42c0c22db31102ca489bcef2bfebf81e1 Mon Sep 17 00:00:00 2001 From: Jakub Jelen Date: Oct 25 2020 20:38:07 +0000 Subject: Drop reference to the strength of encryption -- it is negotiated during key exchange and it can be 256-bit encryption too --- diff --git a/modules/system-administrators-guide/pages/infrastructure-services/OpenSSH.adoc b/modules/system-administrators-guide/pages/infrastructure-services/OpenSSH.adoc index c3821c3..d66cefa 100644 --- a/modules/system-administrators-guide/pages/infrastructure-services/OpenSSH.adoc +++ b/modules/system-administrators-guide/pages/infrastructure-services/OpenSSH.adoc @@ -36,9 +36,9 @@ The SSH protocol provides the following safeguards: No one can pose as the intended server:: After an initial connection, the client can verify that it is connecting to the same server it had connected to previously. -No one can capture the authentication information:: The client transmits its authentication information to the server using strong, 128-bit encryption. +No one can capture the authentication information:: The client transmits its authentication information to the server using strong encryption. -No one can intercept the communication:: All data sent and received during a session is transferred using 128-bit encryption, making intercepted transmissions extremely difficult to decrypt and read. +No one can intercept the communication:: All data sent and received during a session is transferred using strong encryption, making intercepted transmissions extremely difficult to decrypt and read. Additionally, it also offers the following options: