-1

This question already has an answer here:

Assume a client authenticates using the password, which includes hashing and salting. The hash values are stored in a remote database server.

Questions:

  1. For the hash values stored in the database side, salt is added already?

  2. The client sends the hash value to server for authentication. Is the salt added in this transmitted hash value? If yes, how can the client generate the same salt as server? If not, how to ensure the salt is same for both client and server?

  3. In real-life, what are the common ways to securely generate and store salt?

  4. How to periodically change the salt?

marked as duplicate by Matthew, Jeroen - IT Nerdbox, Jacco, schroeder Jul 6 '18 at 8:46

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    Now it is entirely a duplicate of the other question. Also, clients should not be passing hashes, but the password. Why would you want to change the salt? – schroeder Jul 6 '18 at 8:46
0

Most companies I know of are doing (or are moving towards) randomly-salted bcrypt, and the more security-aware usually add some sort of multi factor option like Time-based One Time Passwords.

Not the answer you're looking for? Browse other questions tagged or ask your own question.