bugtraq - Re: [HACKERS] 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: <20050421213354.GH29028@ns.snowman.net>
Date: Thu, 21 Apr 2005 17:33:54 -0400
From: Stephen Frost <sfrost@...wman.net>
To: Mike Fratto <mfratto@....com>
Cc: "'Jim Knoble'" <jmknoble@...ox.com>, bugtraq@...urityfocus.com
Subject: Re: [HACKERS] Postgres: pg_hba.conf, md5, pg_shadow, encrypted passwords

* Mike Fratto (mfratto@....com) wrote:
> Since the salt is known, it has no effect on the "keyspace" because you
> don't have to guess it.  If there was no salt, then pre-computing a
> dictionary is a much smaller task. 

That's the whole point of the discussion- the way Postgres's pg_shadow
stuff works the salt is known and *because* of that it might as well not
exist since it means that you can pre-compute the keyspace.  Knowing the
salt means you can pre-compute the keyspace ahead of time.  If you don't
know the salt until you've gained access then you'll have to wait till
then to begin computing the keyspace.

I suppose technically you could start pre-computing the keyspace before
then, but then it's a much larger keyspace which makes it much more
difficult.

	Stephen

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)