Best way to store passwords in MYSQL database

Question

Yes I know storing passwords in plain text is not advised Is there a best and easy way to store passwords so that the application remains secure

User · Answer

You should use one way encryption  which is a way to encrypt a value so that is very hard to revers it   I m not familiar with MySQL  but a quick search shows that it has a password   function that does exactly this kind of encryption  In the DB you will store the encrypted value and when the user wants to authenticate you take the password he provided  you encrypt it using the same algorithm function and then you check that the value is the same with the password stored in the database for that user  This assumes that the communication between the browser and your server is secure  namely that you use https

User · Answer

Store a unique salt for the user  generated from username   email for example   and store a password  On login  get the salt from database and hash salt   password Use bcrypt to hash the passwords

User · Answer

Passwords in the database should be stored encrypted  One way encryption  hashing  is recommended  such as SHA2  SHA2  WHIRLPOOL  bcrypt DELETED  MD5 or SHA1   those are older  vulnerable  In addition to that you can use additional per-user generated random string -  salt     salt   MD5  this- gt createSalt       Password   SHA2  postData  Password      salt     createSalt   in this case is a function that generates a string from random characters   EDIT  or if you want more security  you can even add 2 salts   salt1    pass    salt2  Another security measure you can take is user inactivation  after 5  or any other number  incorrect login attempts user is blocked for x minutes  15 mins lets say    It should minimize success of brute force attacks

User · Answer

Hashing algorithms such as sha1 and md5 are not suitable for password storing  They are designed to be very efficient  This means that brute forcing is very fast  Even if a hacker obtains a copy of your hashed passwords  it is pretty fast to brute force it  If you use a salt  it makes rainbow tables less effective  but does nothing against brute force  Using a slower algorithm makes brute force ineffective  For instance  the bcrypt algorithm can be made as slow as you wish  just change the work factor   and it uses salts internally to protect against rainbow tables  I would go with such an approach or similar  e g  scrypt or PBKDF2  if I were you

User · Answer

best to use crypt for password storing in DB  example code     crypted pass   crypt  password       pass from login is the user entered password    crypted pass is the encryption if crypt  pass from login  crypted pass       crypted pass       echo  hello user        documentation    http   www php net manual en function crypt php

User · Answer

First off  md5 and sha1 have been proven to be vulnerable to collision attacks and can be rainbow tabled easily  when they see if you hash is the same in their database of common passwords    There are currently two things that are secure enough for passwords that you can use   The first is sha512  sha512 is a sub-version of SHA2  SHA2 has not yet been proven to be vulnerable to collision attacks and sha512 will generate a 512-bit hash  Here is an example of how to use sha512      lt  php hash  sha512   password     The other option is called bcrypt  bcrypt is famous for its secure hashes  It s probably the most secure one out there and most customizable one too   Before you want to start using bcrypt you need to check if your sever has it enabled  Enter  this code      lt  php if  defined  CRYPT BLOWFISH    amp  amp  CRYPT BLOWFISH        echo  CRYPT BLOWFISH is enabled     else   echo  CRYPT BLOWFISH is not available       If it returns that it is enabled then the next step is easy  All you need to do to bcrypt a password is  note  for more customizability you need to see this How do you use bcrypt for hashing passwords in PHP       crypt  password   salt     A salt is usually a random string that you add at the end of all your passwords when you hash them  Using a salt means if someone gets your database  they can not check the hashes for common passwords  Checking the database is called using a rainbow table  You should always use a salt when hashing   Here are my proofs for the SHA1 and MD5 collision attack vulnerabilities  http   www schneier com blog archives 2012 10 when will we se html  http   eprint iacr org 2010 413 pdf  http   people csail mit edu yiqun SHA1AttackProceedingVersion pdf   http   conf isi qut edu au auscert proceedings 2006 gauravaram06collision pdf and   Understanding sha-1 collision weakness

[php] Best way to store passwords in MYSQL database

Examples related to php