doc: replace "safest" by "most secure" (relay protocol)

This commit is contained in:
Sébastien Helleu 2020-04-17 21:18:58 +02:00
parent a5770a224a
commit 853a91d870
3 changed files with 5 additions and 5 deletions

View File

@ -137,8 +137,8 @@ Notes about option _password_:
* If the option is not given (of if the _handshake_ command is not sent by the
client), _relay_ uses automatically _plain_ authentication (if allowed on
_relay_ side).
* _Relay_ chooses the safest algorithm available on both client and _relay_,
by order of priority from first (safest) to last used:
* _Relay_ chooses the most secure algorithm available on both client and
_relay_, by order of priority from first (most secure) to last used:
. _pbkdf2+sha512_
. _pbkdf2+sha256_
. _sha512_

View File

@ -146,8 +146,8 @@ Notes about option _password_:
* If the option is not given (of if the _handshake_ command is not sent by the
client), _relay_ uses automatically _plain_ authentication (if allowed on
_relay_ side).
* _Relay_ chooses the safest algorithm available on both client and _relay_,
by order of priority from first (safest) to last used:
* _Relay_ chooses the more secure algorithm available on both client and
_relay_, by order of priority from first (most secure) to last used:
. _pbkdf2+sha512_
. _pbkdf2+sha256_
. _sha512_

View File

@ -32,7 +32,7 @@
/*
* this list is sorted from the least secure to the safest algorithm:
* this list is sorted from the least secure to the most secure algorithm:
* "plain" is plain text password, the other values are hash algorithms;
* during negotiation with the client, the highest value in this list matching
* the client supported values is used