Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You should store passwords hashed (and <strong><a href="https://stackoverflow.com/questions/1645161/salt-generation-and-open-source-software/1645190#1645190">properly salted</a></strong>).</p> <p><strong>There is no excuse in the world that is good enough to break this rule.</strong></p> <p>Currently, using <a href="http://www.php.net/crypt" rel="nofollow noreferrer">crypt</a>, with CRYPT_BLOWFISH is the best practice.<br> CRYPT_BLOWFISH in PHP is an implementation of the Bcrypt hash. Bcrypt is based on the Blowfish block cipher.</p> <ul> <li><p>If your client tries to login, you hash the entered password and compare it to the hash stored in the DB. if they match, access is granted.</p></li> <li><p>If your client wants to change the password, they will need to do it trough some little script, that properly hashes the new password and stores it into the DB.</p></li> <li><p>If your client wants to recover a password, a new random password should be generated and send to your client. The hash of the new password is stored in the DB</p></li> <li><p>If your clients want to look up the current password, <em>they are out of luck</em>. And that is exactly the point of hashing password: the system does not know the password, so it can never be 'looked up'/stolen.</p></li> </ul> <p><a href="https://stackoverflow.com/users/1/jeff-atwood">Jeff</a> blogged about it: <a href="http://www.codinghorror.com/blog/archives/000953.html" rel="nofollow noreferrer">You're Probably Storing Passwords Incorrectly</a></p> <p>If you want to use a standard library, you could take a look at: <a href="http://www.openwall.com/phpass/" rel="nofollow noreferrer">Portable PHP password hashing framework</a> and make sure you use the CRYPT_BLOWFISH algorithm.</p> <p>(Generally speaking, messing around with the records in your database directly is asking for trouble.<br> Many people -including very experienced DB administrators- have found that out the hard way.)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is the best way to implement 2-way encryption with PHP?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJacco
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is the best way to implement 2-way encryption with PHP?
      singulars
      1. PTQuestion
    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. COI think you want to edit your first statement to read: "You should store passwords hashed"
      singulars
      1. PO
      1. USJesse Weigert
    2. COEeeeh, yes, thanks :)
      singulars
      1. PO
      1. USJacco
    3. CODid you mean to write Blowfish here? Blowfish == symmetric key encryption, not hashing. I would strongly recommend hashing over encryption.
      singulars
      1. PO
      1. USthomasrutter
 

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