Instead of using md5 and similar (too fast to calculate, and rainbow tables attack too - if not salted) my idea is:
-create a cleartext (even public);
-use the password you want to store to encrypt this text, using aes256 for example;
-save the encrypted text;
verify your password (on user input) encrypting the clear text and checking if it matches with stored encrypted password.
Pros:
-it's more slow to calculate (and so less easy to brute force)
-being the cleartext different on each "server" there's now way to have a rainbow table!
Instead of using md5 and similar (too fast to calculate, and rainbow tables attack too - if not salted) my idea is:
-create a cleartext (even public); -use the password you want to store to encrypt this text, using aes256 for example; -save the encrypted text;
verify your password (on user input) encrypting the clear text and checking if it matches with stored encrypted password.
Pros: -it's more slow to calculate (and so less easy to brute force) -being the cleartext different on each "server" there's now way to have a rainbow table!
opinions? cheers, aw4y