diff options
| author | Mattias Andrée <m@maandree.se> | 2026-05-14 15:55:33 +0200 |
|---|---|---|
| committer | Mattias Andrée <m@maandree.se> | 2026-05-14 15:55:33 +0200 |
| commit | 4e6f25806e3c9fa4753ce959ef990167796acd32 (patch) | |
| tree | e641de9953f5b58afc1f36efe9c42a0d20254cd2 /README | |
| parent | Fix libtest and add file descriptor leak detection (diff) | |
| download | librecrypt-4e6f25806e3c9fa4753ce959ef990167796acd32.tar.gz librecrypt-4e6f25806e3c9fa4753ce959ef990167796acd32.tar.bz2 librecrypt-4e6f25806e3c9fa4753ce959ef990167796acd32.tar.xz | |
Tests and fixes
Signed-off-by: Mattias Andrée <m@maandree.se>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -100,5 +100,19 @@ DESCRIPTION Get encoding alphabet for the last algorithm in a chain. +NOTES + Using librecrypt_add_algorithm(3) to hash existing password + hashes should be used as a transitional mitigation strategy + when replaing an old password hash function. Once the password + is available in clear text, it should be hashed anew using + only the new password hash function: this will both increase + security and reducing login it, allowing for stronger hash + function configurations. This is especially important if the + password is actually a key and longer than the old hash. It + is also a good idea to force password reset, and lock any + account that hasn't reset its password, because it is + possibly that the old password hashes has been leaked and it + will force a fresh hashing even one counts that seldom log in. + SEE ALSO crypt(3), crypt(5) |