php存密码,PHP 加密存储模型

用户评论:

seigoryu at hotmail dot de (2012-10-04 08:30:56)

I would strongly recommend using SHA-2 or better the new SHA-3 hash algorithm. MD5 is practically unusable, since there are very well working rainbow tables around the whole web. Almost the same for SHA-1. Of course you should never do a hash without salting!

Reiner (2011-04-21 00:46:06)

Using functions to obfuscate the hash generation does not increase security. This is security by obscurity. The algorithm used to hash the data needs to be secure by itself.

I would not suggest to use other data as salt. For example if you use the username, you won't be able to change the values without rehashing the password.

I would use a dedicated salt value stored in the same database table.

Why? Because a lot of users use the same login credentials on different web services. And in case another service also uses the username as salt, the resulting hashed password might be the same!

Also an attacker may prepare a rainbow table with prehashed passwords using the username and other known data as salt. Using random data would easily prevent this with little programming effort.

zyppora at nosmac yahoo dot com (2007-03-14 04:30:23)

In addition to roysimkes at hotmail dot com:

If your passwords are so secret that they're worth a year's hacking/cracking/etc, you might want to consider 'password renewal', much like Windows' option. Tell your users to renew their passwords every x days/weeks/months to make it extra hard on those already-sweating malicious visitors.

somebody (2006-12-26 22:07:19)

A better way to hash would be to use a separate salt for each user. Changing the salt upon each password update will ensure the hashes do not become stale.

Fairydave at the location of dodo.com.au (2006-02-11 18:58:14)

I think the best way to have a salt is not to randomly generate one or store a fixed one. Often more than just a password is saved, so use the extra data. Use things like the username, signup date, user ID, anything which is saved in the same table. That way you save on space used by not storing the salt for each user.

Although your method can always be broken if the hacker gets access to your database AND your file, you can make it more difficult. Use different user data depending on random things, the code doesn't need to make sense, just produce the same result each time. For example:

if ((asc(username character 5) > asc(username character 2))

{

if (month the account created > 6)

salt = ddmmyyyy of account created date

else

salt = yyyyddmm of account created date

}

else

{

if (day of account created > 15)

salt = user id * asc(username character 3)

else

salt = user id + asc(username character 1) + asc(username character 4)

}

This wont prevent them from reading passwords when they have both database and file access, but it will confuse them and slow them up without much more processing power required to create a random salt