-
Recently Browsing 0 members
- No registered users viewing this page.
-
Similar Content
-
Microsoft Authenticator users: Your password auto-fill is dying soon - this is what to do
By zikalify,
- microsoft
- microsoft authenticator
- (and 6 more)
- 9 replies
- 0 views
-
Microsoft is killing its password manager in Authenticator to make everyone use Edge 1 2
By TarasBuria,
- microsoft
- microsoft authenticator
- (and 4 more)
- 47 replies
- 0 views
-
iOS 18 makes it easier to share Wi-Fi passwords with Android users
By Aditya Tiwari,
- 5 replies
- 1 view
-
X launches passkeys as a new way to login to its iOS app in the U.S. without passwords
By Anushe Fawaz,
- 2 replies
- 6 views
-
Microsoft Edge to get improved password manager with notes and categories
By TarasBuria,
- microsoft
- microsoft edge
- (and 8 more)
- 6 replies
- 6 views
-
Question
SuperKid
Hi,
When you hash a password using a method like SHA1, BCrypt etc you provide a salt key, but I was wondering do you reuse one salt key throughout or generate a unique random salt key for each password you generator and store it?
I have seen both methods use, some people store in the database the salt key with the users password where both are unique or some people have one salt key they reuse to hash all passwords, which method is usually best?
Matt.
Link to comment
https://www.neowin.net/forum/topic/1213485-hashing-a-password/Share on other sites
3 answers to this question
Recommended Posts