security - Encrypted passwords of not-encrypted passwords user base -
Some time back I joined the new project, it was for a very long time for development. I was surprised that all users' passwords are stored in non-encrypted form .
I explained our management to this great security vulnerabilities - it seems that they agree with that and the members of the team also agree to make the project more secure.
We have around 20K users in the system.
Actually it is quite stressful to work - Migrate non-encrypted passwords in encrypted form . If something goes wrong, then the project can be disaster.
How can I reduce this stress? Backup? Unit Tests (Integrated Testing)?
Good, be careful of your backup because it contains unencrypted user password: -)
1) Create a secure backup of the entire table data
P> 2) Create new column (password encrypted or same name)
3) Using 32 bytes or large salt, each row new column with MD5 Use to update with unencrypted password. There are many MD5 functions in every database system today, so you do not even need to leave your SQL prompt.
4) Keep plain text column in the interim and work with salt accordingly Update App / Script Password
5) To move it out of play temporarily rename the old password column in plain text - and if there is a problem, go back to step 4 and fix your mistakes.
6) When everything is working properly, drop plain text password columns
7) Encourage users to choose a new password so that you have any previous Some levels of security have been successful to reduce the impact of the attacks.
Comments
Post a Comment