Re: Best way to HIDE passwords that are in a table



One common method of storing passwords securely in a database is to use a
one-way hash function on the password and store the hashed value in the
database instead of encrypting it. You'll probably want to use an
SHA-family (or other secure) hash function (MD5-family hashes and many other
hash functions are not considered secure). Using this method you'll do
something like this:

-Initially you hash the password and store the hashed value in the database
in a VARBINARY or BINARY column.
-When you need to validate, accept an input string from the user and hash
that string using the same algorithm. Then compare the hashed user input
string to the hash of the password stored in the database.

The down-side is that once you hash a password you can't retrieve it's
original value as you can with encryption/decryption (hence the term
"one-way hash"). This is generally not a problem, however. You can perform
the hashes client-side with .NET or the Windows CryptoAPI or server-side
with extended procedures like these
http://www.sqlservercentral.com/columnists/mcoles/sql2000dbatoolkitpart1.asp

Other options include using .NET or CryptoAPI to encrypt/decrypt your
password client side, or using server-side extended procedures to do the
job.

"MSUTech" <MSUTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D6620EA-05C0-4044-9D1B-497261028F16@xxxxxxxxxxxxxxxx
Hello All,

If I am storing passwords in a table within SQL Server 2000. Is there a
way
to ENCRYPT or HIDE the passwords, so that when I run a SELECT statement, I
can not see them?

If this is not possible, what is the recommended way to HIDE passwords
from
the SQL Server Administrator?

thans...


.



Relevant Pages

  • Re: Newbie - Is this Reasonable?
    ... because this hash is stored in the database. ... So you use PKCS5v2 to generate a key hash from a salt and the user's passphrase, then store the salt and the hash in a database. ... are even more critical in database applications because the payoff from tampering with selected fields may be much higher, fields tend to be fixed-length so it's easier to tamper with them in a meaningful way, and databases lend themselves to off-line analysis, so the attacker can marshall more resources and take more time to attack your system. ... You're using a stream cipher for encryption. ...
    (sci.crypt)
  • Re: CRC and secure hashes
    ... to build a secure 2-universal hash function. ... 2-univ hash function, for appropriate parameter choices. ... There are various ways to build a secure MAC out of a 2-univ hash ...
    (sci.crypt)
  • Re: looking for help with a counting algorithm
    ... >> subcategory is counted, the code goes back up the tree to the root, adding ... >> involve retrieving all the category memberships from the database, ... sub ReadCategories{ ... ReadCategories is called with two empty hash pointers by any of the ...
    (comp.lang.perl.misc)
  • Re: 42nd Known Mersenne Prime Found == 2^25,964,951-1 == The number has 7,816,230 digits
    ... constructed for the larger Mersenne primes. ... Let us say that one wishes to have a secure hash function. ...
    (sci.crypt)
  • Re: Secure Password in database
    ... Subject: Secure Password in database ... > in database as SHA hash. ... You don't want to be able to compromise the client, ... get a bunch of garbage back when you try to get the 2-way encrypted data. ...
    (SecProg)