Databases
StackOverflow2013
Postsdbo
POHow do you securely store a user's password and salt in MySQL?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do you securely store a user's password and salt in MySQL?
    primarykey
    data
    text
    <p>So, I found out on SO that you're supposed to hash the password together with a "salt". (The articles can be found <a href="https://stackoverflow.com/questions/6879706/securely-hash-passwords-so-much-conflicting-advice/6879902">here</a> and <a href="https://stackoverflow.com/questions/401656/secure-hash-and-salt-for-php-passwords">here</a>.)</p> <p>Here's the code:</p> <pre><code>$password = 'fish'; /* should be "unique" for every user? */ $salt= 'ABC09'; $site_key = 'static_site_key'; hash_hmac('sha1', $password . $salt, $site_key); </code></pre> <p>And now I need to save both the <code>$password</code> and <code>$salt</code> in MySQL, like so:</p> <pre><code>+---------+--------+----------+-------+ | user_id | name | password | salt | +---------+--------+----------+-------+ | 1 | krysis | fish** | ABC09 | +---------+--------+----------+-------+ </code></pre> <p>** <code>fish</code> will of course be hashed and not stored in plain text.</p> <p>And I'm just wondering whether or not it actually makes sense to do it this way, because this way a hacker or whoever will also know the salt? So, if they crack the password and the see it's <code>fishABC09</code> they automatically will know the password is <code>fish</code>? Or might he "never" be able to crack the password because he doesn't know the <code>secret_key</code>, as it isn't stored in the database?</p> <p>I'm sorry if I'm not making any sense. I just always used <code>sha1</code> for passwords, and today I found these articles that talked about adding a <code>salt</code>.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. This table or related slice is empty.
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do you securely store a user's password and salt in MySQL?
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POHow do you securely store a user's password and salt in MySQL?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do you securely store a user's password and salt in MySQL?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload