docs-archive/sysadmin-guide
Archived
21
1
Fork 3
Code Issues 26 Pull requests 2 Activity

Drop reference to the strength of encryption -- it is negotiated during key exchange and it can be 256-bit encryption too

Browse source
This commit is contained in:
Jakub Jelen 2020-07-14 09:33:09 +02:00 • committed by pbokoc
commit c03da3a42c
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/system-administrators-guide/pages/infrastructure-services/OpenSSH.adoc
View file

@ -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: