Re: SQL Storing Passwords?

[Jeffrey Walton <noloader () gmail com>]

> First of all, storing salts next to a hash is not bad design, it
> perfect. Why?
Sorry to play language lawyer here.... Gatuam said "Key", not "Salt":
"...so the hashing is done like this SSHA('mypassword','key')"

Keys are private parameters and salts are public parameters. If you
want to treat a salt as a key, it needs to be appropriately protected.

I was recently reading a paper from John Steven of Cigital and OWASP
on Password Security. His threat models required the use both keys and
salts. For organizations that have the resources, the key goes in an
HSM (unlikely in a Mom-and-Pop shop).

Jeff

On Tue, Sep 4, 2012 at 7:38 AM, Alexander Meesters
<a.meesters () sansyl com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hello,
>
> First of all, storing salts next to a hash is not bad design, it
> perfect. Why?
>
> Well, now if somebody want to crack them using rainbow tables, then
> need to regenerate the rainbow table every time the user changes. This
> will really slow down the whole process of cracking and might even
> make the unsub give up the project as a whole. At least it will buy
> you some time to get users to change the passwords once you detected
> your breach.
>
> On 09/04/2012 12:10 PM, Gautam wrote:
> > Hi Jim,
> >
> > The PWD in the table should be the actual hash of your password,
> > however they don't seem to be basic hash in your case.
> >
> > They are salted and the key values in your table are the salt.
> >
> > so the hashing is done like this SSHA('mypassword','key')
> >
> > From my point of view keeping the passwords and the key in the
> > same table is a poor design, however that's what a developer
> > generally do so that he can manage everything in one space.
> >
> > if you want to verify take a known password and take a 'key' value
> > from your table and you will notice that you will get the value
> > from the "pwd" field. Just check what hashing is used.
> >
> >
> > Notice this on crackstation.net 'Enter up to 10 non-salted hashes:
> > ' :-) . that's why it will not give you any results.
> >
> >
> > On Thu, Aug 30, 2012 at 11:07 PM, Greg Merideth
> > <gmerideth () uclnj com> wrote:
> > > If it ends in an "=" sign it's more than likely base64 encoded
> > > text.  It could have been encrypted before and then stored in
> > > base64 so it may be gibberish but try running it through a base64
> > > decoder and see what you get.
> > >
> > >
> > > .:.:.:.:.:.:. Greg Merideth President/Chief Problem Solver United
> > > Computer Technologies gmerideth () uclnj com
> > > http://www.facebook.com/uclnj
> > >
> > > -----Original Message----- From: listbounce () securityfocus com
> > > [mailto:listbounce () securityfocus com] On Behalf Of
> > > jim.jones12 () gmail com Sent: Wednesday, August 29, 2012 4:49 PM
> > > To: security-basics () securityfocus com Subject: SQL Storing
> > > Passwords?
> > >
> > > Hello, I'm looking for so help, i've come across a user table
> > > within SQL 2008 that contains two columns "Pwd" & "Key" and
> > > concerned they may contain our users Active Directory
> > > credentials.  The Pwd column contains what appears to be a 40
> > > character hash (uppercase) and the Key column has a random 8
> > > character key that ends in "=".  I've tried running the Pwd
> > > string through crackstation.net but to not avail.  The same user
> > > tables also contains a column for username and full name.  I
> > > guess with the recent Linkedin and Philips hack I may be a little
> > > over paranoid.
> > >
> > > Could someone point me in the right direction on what I can to do
> > > validate this information?

------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, how 
it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, 
install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are 
highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
------------------------------------------------------------------------