Jump to content

Recommended Posts

Very interesting Dan and it makes a lot of sense now.  What about using both md5 and sha1 and salt and concatenating them all together?  Would that be another layer of defense?  Or maybe 2 password fields stored in the database, one with the md5 data and one with the sha1 data?

If you're starting from scratch you should check the article in my signature.

 

SHA1 is too fast an algorithm to trust for password hashing, nor was it designed for it.

 

Storing 2 hashes is redundant. Having 50 passwords will always be more secure than 1, but if you're going to go that far you're better off using a single, large key of some sort.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.