From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Marko Kreen <markokr(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] fix dblink security hole |
Date: | 2008-09-21 17:58:29 |
Message-ID: | 48D68B45.7060805@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marko Kreen wrote:
> On 9/21/08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Joe Conway <mail(at)joeconway(dot)com> writes:
>>> Good point -- I'll look into that and post something tomorrow. How does
>> > "requirepassword" sound for the option? It is consistent with
>> > "requiressl" but a bit long and hard to read. Maybe "require_password"?
>>
>>
>> Well, no, because it's not requiring a password.
>>
>> Perhaps "ignore_pgpass"?
>
> You need to ignore pg_service also. (And PGPASSWORD)
Why? pg_service does not appear to support wildcards, so what is the
attack vector?
And on PGPASSWORD, the fine manual says the following:
PGPASSWORD sets the password used if the server demands password
authentication. Use of this environment variable is not recommended
for security reasons (some operating systems allow non-root users to
see process environment variables via ps); instead consider using the
~/.pgpass file (see Section 30.13).
At the moment the only real issue I can see is .pgpass when wildcards
are used for hostname:port:database.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-21 18:01:58 | Re: Proposal: move column defaults into pg_attribute along with attacl |
Previous Message | Joshua D. Drake | 2008-09-21 17:39:44 | Re: Proposal: move column defaults into pg_attribute along with attacl |