Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Bugtraq
[Top] [All Lists]

Re: [HACKERS] Postgres: pg_hba.conf, md5, pg_shadow, encrypted

Subject: Re: [HACKERS] Postgres: pg_hba.conf, md5, pg_shadow, encrypted
Date: Thu, 21 Apr 2005 09:32:08 -0400
On Thu, 2005-04-21 at 11:06 +0200, Tino Wildenhain wrote:
Am Mittwoch, den 20.04.2005, 16:23 -0500 schrieb Jim C. Nasby:
On Wed, Apr 20, 2005 at 05:03:18PM -0400, Tom Lane wrote:
...
Simply put, MD5 is no longer strong enough for protecting secrets. It's
just too easy to brute-force. SHA1 is ok for now, but it's days are
numbered as well. I think it would be good to alter SHA1 (or something
stronger) as an alternative to MD5, and I see no reason not to use a
random salt instead of username.

I wonder where you want to store that random salt and how this would add
to the security.

One advantage of a random salt would be that the username can be changed
without having to reset the password at the same time.

-- 

<Prev in Thread] Current Thread [Next in Thread>