Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <pre><code>function encodePwd($salt, $string) { return sha1( $salt . $string ); } </code></pre> <p>think about salt randomization for a minute though. Password encoding specifically. </p> <p>If i have salt of "random" and a password of "complex", my sha1 would be </p> <pre><code>e55ec45f2873a04d2b888a5f59dd3f9d3bb25329 </code></pre> <p>that's stored in the database. I want to check against that. </p> <p>So when a user supplies me "complex" as a password, i tag "random" in front of it and encode it to get the same hash. If they equal, then bazinga! i'm set. </p> <p>But what if that was random?</p> <p>salt when it was stored: "random"</p> <pre><code>SHA1: e55ec45f2873a04d2b888a5f59dd3f9d3bb25329 </code></pre> <p>salt when the user put it in: "apple"</p> <pre><code>SHA1: e07b207d77a0bd27d321552fc934b186559f9f42 </code></pre> <p>how am i going to match those?</p> <p>If you are looking for a more secure method, use data that you <em>have</em> and that is <em>constant</em> like the username or id of user or something (preferably something that won't change). You need a pattern you can rely on. </p> <p>username would work good (you'd have to make sure to update password if they ever changed the username) that way authentication could look like </p> <pre><code>`WHERE `username` = '&amp;username' AND `password` = '" . encodePwd( $username, $password ) . "'"` function encodePwd( $username, $password) { // maybe modify username on a non-random basis? - like // $username = sha1( substr($username, 2)); // assuming usernames have a min-length requirement return sha1( $username . $password ) ; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCan someone point me to a good PHP/MySQL salted hashed password implementation?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDan Heberden
    1. USDan Heberden
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHow is the salt randomized? How is that salt used when authenticating the password upon login? Looking for a bit more depth here. Thanks!
      singulars
      1. PO
      1. USbarfoon
    2. CO@barfoon are you **really** want your salt to be randomized?
      singulars
      1. PO
      1. USYour Common Sense
    3. CO@Col.Shrapnel: Indeed, per-entity - e.g. have a different salt for each user's password. (and using bcrypt instead of sha1 would not hurt either)
      singulars
      1. PO
      1. USPiskvor
 

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