bugtraq - Re: Postgres: pg_hba.conf, md5, pg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1114090328.66326.90.camel@home>
Date: Thu, 21 Apr 2005 09:32:08 -0400
From: Rod Taylor <pg@....ca>
To: Tino Wildenhain <tino@...denhain.de>
Cc: bugtraq@...urityfocus.com, pgsql-hackers@...tgresql.org,
   Stephen Frost <sfrost@...wman.net>, Tom Lane <tgl@....pgh.pa.us>,
   "Jim C. Nasby" <decibel@...ibel.org>
Subject: Re: Postgres: pg_hba.conf, md5, pg_shadow, encrypted

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.

-- 

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend