Re: Salt in encrypted password in pg_shadow

From: David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Salt in encrypted password in pg_shadow
Date: 2004-09-08 05:59:17
Message-ID: 413E9FB5.7090802@zara.6.isreserved.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
>>Hm, I thought the purpose of salt is generally well understood?
>
> Apparently not.
>
> The purpose of salting the encrypted passwords in pg_shadow is *not* to
> protect them against attackers who have somehow managed to
> illegitimately read pg_shadow. (As I explained before, such attackers
> are effectively superuser already, and so protecting the superuser
> password from them is not nearly as interesting as all that.) The
> purpose is to prevent unscrupulous DBAs from deducing the cleartext
> passwords being used by their users. Since the users presumably are not
> all named "postgres", the argument you are advancing is not relevant.

Then I'd say the purpose is wrong. There is not much hope in protecting
unscrupulous DBAs from getting their users' password anyway (they can
most probably sniff traffic, trap/log queries, or shut down postmaster
and replace it with a trojan binary).

The purpose of a salt, by most definition, should be to discourage
dictionary attack.

Anyway, I think we've agreed that the current protocol need not be
changed, on the basis of too much pain caused. But there's no reason not
to use random salt in future protocol. It offers the benefit you
mentioned plus protects against dictionary attack.

--
dave

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Secomb 2004-09-08 06:05:10 ERROR: parser: unterminated quoted string
Previous Message Mike Nolan 2004-09-08 04:59:24 Re: Salt in encrypted password in pg_shadow