The only reason you would salt passwords in a database means your concerned that the password db table has been compromised... if you fear that has happened then the salt that your storing in the database is available to the attacker. Thus adding md5 or sha1 or sha256 of that salt to the password is no more secure than just appending the salt in plaintext. The same number of computations will be required to "crack" the password hash.<br>
<br>-Matt<br><br>PS. md5/sha1 are not cryptographically secure hash algorithms anymore (however probably are ok for this situation). any sha2 algorithm (sha256, sha512) is suposedly.<br><br><div class="gmail_quote">On Mon, Mar 10, 2008 at 11:32 AM, Mark Wu <<a href="mailto:markplace@gmail.com">markplace@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">><br>
> How much more secure is than simply:<br>
><br>
> md5($password . $private_key)<br>
<br>
</div>Actually, it's no difference for normal people, but much secure for those<br>
hackers...<br>
<br>
BTW, VBB and IPB use:<br>
<br>
md5(md5($password).md5($private_key))<br>
<div class="Ih2E3d"><br>
><br>
> And are there any downsides of the new method - ie. will it<br>
> fail on upgrades, or fail for certain servers, etc?<br>
><br>
<br>
</div>mmm .... for lifetype 2.0 . The minimal requirement is php 5.1.x ...<br>
<br>
so, It won't be a problem.<br>
<br>
mhash become "hash" in pecl in php5, if there is no hash installed, it will<br>
use the pure php implementation...<br>
<div><div></div><div class="Wj3C7c"><br>
><br>
> On Mon, 10 Mar 2008, Mark Wu wrote:<br>
><br>
> > Here comes more secure algorithm:<br>
> ><br>
> > sha256(md5($password)+md5($your_provide_private_key));<br>
> ><br>
> > I use sha256 here.<br>
> ><br>
> > Here also comes the pure php sha256 implementation:<br>
> ><br>
> > <a href="http://nanolink.ca/pub/sha256/" target="_blank">http://nanolink.ca/pub/sha256/</a><br>
> ><br>
> > If the server has "hash" pecl, it will use it instead of<br>
> the pure one.<br>
> ><br>
> > Mark<br>
> ><br>
> >> -----Original Message-----<br>
> >> From: <a href="mailto:plog-svn-bounces@devel.lifetype.net">plog-svn-bounces@devel.lifetype.net</a><br>
> >> [mailto:<a href="mailto:plog-svn-bounces@devel.lifetype.net">plog-svn-bounces@devel.lifetype.net</a>] On Behalf Of Reto Hugi<br>
> >> Sent: Monday, March 10, 2008 7:25 PM<br>
> >> To: LifeType Developer List<br>
> >> Subject: Re: [pLog-svn] Salted MD5<br>
> >><br>
> >> Hi Mark<br>
> >><br>
> >> I welcome your suggestion and think that this is valuable<br>
> >> protection against rainbow table attacks.<br>
> >><br>
> >> We already had an issue with the revealed admin password<br>
> >> hash. This would have been less severe with the saltet md5.<br>
> >><br>
> >> Thanks for suggesting!<br>
> >><br>
> >> reto<br>
> >><br>
> >> Mark Wu wrote:<br>
> >>> Hi All:<br>
> >>><br>
> >>> I plan to upgrade our password algorithm to salted MD5, take the<br>
> >>> following for eaxample:<br>
> >>><br>
> >>> sha1(md5($password) + user_defined_private_key);<br>
> >>><br>
> >>> I will also remain an option in lifetype admin panel for<br>
> >> user to use<br>
> >>> the old MD5 way to keep compatability.<br>
> >>><br>
> >>> If we use the algorithm above, It is also possible to<br>
> >> convert the old<br>
> >>> hashed password to new hased password.<br>
> >>><br>
> >>> How do you think?<br>
> >>><br>
> >>><br>
> >><br>
> <a href="http://kuza55.blogspot.com/2006/10/online-reverse-lookup-tables-for.ht" target="_blank">http://kuza55.blogspot.com/2006/10/online-reverse-lookup-tables-for.ht</a><br>
> >>> ml<br>
> >>><br>
> >>> These kind of online reverse lookup table sites making<br>
> the MD5 only<br>
> >>> algorithm more dangerous.<br>
> >>><br>
> >>> Mark<br>
> >>><br>
> >>><br>
> >>><br>
> >>><br>
> >>><br>
> >><br>
> ----------------------------------------------------------------------<br>
> >>> --<br>
> >>><br>
> >>> _______________________________________________<br>
> >>> pLog-svn mailing list<br>
> >>> <a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>
> >>> <a href="http://limedaley.com/mailman/listinfo/plog-svn" target="_blank">http://limedaley.com/mailman/listinfo/plog-svn</a><br>
> >><br>
> >> _______________________________________________<br>
> >> pLog-svn mailing list<br>
> >> <a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>
> >> <a href="http://limedaley.com/mailman/listinfo/plog-svn" target="_blank">http://limedaley.com/mailman/listinfo/plog-svn</a><br>
> ><br>
> > _______________________________________________<br>
> > pLog-svn mailing list<br>
> > <a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>
> > <a href="http://limedaley.com/mailman/listinfo/plog-svn" target="_blank">http://limedaley.com/mailman/listinfo/plog-svn</a><br>
> ><br>
><br>
> --<br>
> Jon Daley<br>
> <a href="http://jon.limedaley.com/" target="_blank">http://jon.limedaley.com/</a><br>
><br>
> We are all made different, but we are all sinners.<br>
> -- Jim Herron<br>
> _______________________________________________<br>
> pLog-svn mailing list<br>
> <a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>
> <a href="http://limedaley.com/mailman/listinfo/plog-svn" target="_blank">http://limedaley.com/mailman/listinfo/plog-svn</a><br>
<br>
_______________________________________________<br>
pLog-svn mailing list<br>
<a href="mailto:pLog-svn@devel.lifetype.net">pLog-svn@devel.lifetype.net</a><br>
<a href="http://limedaley.com/mailman/listinfo/plog-svn" target="_blank">http://limedaley.com/mailman/listinfo/plog-svn</a><br>
</div></div></blockquote></div><br>