Skip to content

Commit

Permalink
Update cheatsheets/Password_Storage_Cheat_Sheet.md
Browse files Browse the repository at this point in the history
Co-authored-by: Shlomo Zalman Heigh <shlomo.heigh@cyberark.com>
  • Loading branch information
jmanico and szh authored Nov 18, 2023
1 parent ca9377b commit 35b2c5b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion cheatsheets/Password_Storage_Cheat_Sheet.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ The most common approach to upgrading the work factor is to wait until the user

Some modern hashing algorithms have been specifically designed to securely store passwords. This means that they should be slow (unlike algorithms such as MD5 and SHA-1, which were designed to be fast), and you can change how slow they are by changing the work factor.

You do not need to hide which password hashing algorithm that is used by a website. If you utilize a modern password hashing algorithm with proper configuration parameters, it should be safe to state in public which password hashing algorithms are in use and be listed [here](https://pulse.michalspacek.cz/passwords/storages).
You do not need to hide which password hashing algorithm is used by an application. If you utilize a modern password hashing algorithm with proper configuration parameters, it should be safe to state in public which password hashing algorithms are in use and be listed [here](https://pulse.michalspacek.cz/passwords/storages).

Three hashing algorithms that should be considered (see below):

Expand Down

0 comments on commit 35b2c5b

Please sign in to comment.