Content-Type: text/plain; charset=UTF-8
Cc: Guillaume Lelarge <guillaume@lelarge.info>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: DROP TABLE can be issued by schema owner as well as table owner
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Derrick Rice <derrick.rice@gmail.com>
In-reply-to: <BANLkTimfjeEE-2EVnghk0HPynMNvMpMFmQ@mail.gmail.com>
References: <BANLkTikpQfBj8EMwjwrA1kXOF1F8J4H6Hw@mail.gmail.com>
	<4DD69445.3070507@lelarge.info>
	<BANLkTimfjeEE-2EVnghk0HPynMNvMpMFmQ@mail.gmail.com>
Date: Fri, 20 May 2011 12:53:49 -0400
Message-Id: <1305910393-sup-7762@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Derrick Rice's message of vie may 20 12:35:24 -0400 2011:
> On Fri, May 20, 2011 at 12:18 PM, Guillaume Lelarge
> <guillaume@lelarge.info>wrote:
> 
> > Well, for a specific object, any superuser, the database owner, the
> > schema owner, and the object owner could drop the object. This is not a
> > vulnerability.
> >
> 
> It is not documented clearly.  Any information not made clear is an
> opportunity for an error which leads to a vulnerability.

So we need a standard caveat stmt on all relevant pages?  Seems
reasonable to me.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support