Changing mis-formatted definition list of hashing algorithms to a table

Closes #35416

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
This commit is contained in:
Alexander Schwartz 2024-11-28 14:44:14 +01:00 committed by Pedro Igor
parent 3c33a7180e
commit b98cd12b58

View File

@ -28,12 +28,25 @@ The new policy will not be effective for existing users. Therefore, make sure th
Passwords are not stored in cleartext. Before storage or validation, {project_name} hashes passwords using standard hashing algorithms.
Supported password hashing algorithms include:
Supported password hashing algorithms are shown in the following table.
* argon2:: Argon2 (default for non-FIPS deployments)
* pbkdf2-sha512:: PBKDF2 with SHA512 (default for FIPS deployments)
* pbkdf2-sha256:: PBKDF2 with SHA256
* pbkdf2:: PBKDF2 with SHA1 (deprecated)
[%autowidth,cols="m,"]
|===
|Hashing algorithm |Description
| argon2
| Argon2 (default for non-FIPS deployments)
| pbkdf2-sha512
| PBKDF2 with SHA512 (default for FIPS deployments)
| pbkdf2-sha256
| PBKDF2 with SHA256
| pbkdf2
| PBKDF2 with SHA1 (deprecated)
|===
It is highly recommended to use Argon2 when possible as it has significantly less CPU requirements compared to PBKDF2, while
at the same time being more secure.
@ -52,12 +65,25 @@ If you change the hashing algorithm, password hashes in storage will not change
===== Hashing iterations
Specifies the number of times {project_name} hashes passwords before storage or verification. The default value is -1,
which uses the default hashing intervals for the selected hashing algorithm:
which uses the default hashing iterations for the selected hashing algorithm as listed in the following table.
* argon2:: 5
* pbkdf2-sha512:: 210,000
* pbkdf2-sha256:: 600,000
* pbkdf2:: 1,300,000
[%autowidth,cols="m,>"]
|===
|Hashing algorithm |Default hash iterations
| argon2
| 5
| pbkdf2-sha512
| 210,000
| pbkdf2-sha256
| 600,000
| pbkdf2
| 1,300,000
|===
[NOTE]
====