Timeline for answer to Password hashes do not match with bcrypt (python) by Simon1
Current License: CC BY-SA 4.0
Post Revisions
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2025 at 6:50 | comment | added | Kenzo Staelens |
it's more likely that checkpw takes the original salt used, because it's just right there stored in the password hash from wikipedia $ algo$ cost$ salt hash then just hashes the to check password with that salt and compares (yes, it's just fine to store salts in the database because they only exist to break rainbow tables)
|
|
| May 30, 2025 at 3:56 | comment | added | Frank Yellin | Look at the wikipedia on article on bcrypt to see how the output from bcrypt encodes the algorithm, the cost, the salt, and the "hash". You have to pull out all of the fields, pass them as input to bcrypt and include what the user types as the password, and confirm that it equals the same output. | |
| May 30, 2025 at 3:02 | history | answered | Simon1 | CC BY-SA 4.0 |
