From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_ls_dir & friends still have a hard-coded superuser check |
Date: | 2017-01-29 22:39:56 |
Message-ID: | 20170129223956.GB17445@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 26, 2017 at 08:50:27AM -0500, Robert Haas wrote:
> On Wed, Jan 25, 2017 at 10:31 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Frankly, I get quite tired of the argument essentially being made
> > here that because pg_ls_dir() wouldn't grant someone superuser
> > rights, that we should remove superuser checks from everything.
> > As long as you are presenting it like that, I'm going to be quite
> > dead-set against any of it.
> 1. pg_ls_dir. I cannot see how this can ever be used to get
> superuser privileges.
With pilot error, all things are possible. A file name under $PGDATA
could be the superuser password.
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-01-29 22:52:51 | Re: pg_ls_dir & friends still have a hard-coded superuser check |
Previous Message | Jim Nasby | 2017-01-29 21:49:18 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |