Message-ID: <4DD6A3CA.3060302@lelarge.info>
Date: Fri, 20 May 2011 19:24:26 +0200
From: Guillaume Lelarge <guillaume@lelarge.info>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Alvaro Herrera <alvherre@commandprompt.com>
CC: Derrick Rice <derrick.rice@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: DROP TABLE can be issued by schema owner as well as table
 owner
References: <BANLkTikpQfBj8EMwjwrA1kXOF1F8J4H6Hw@mail.gmail.com>
	<4DD69445.3070507@lelarge.info>
	<BANLkTimfjeEE-2EVnghk0HPynMNvMpMFmQ@mail.gmail.com>
	<1305910393-sup-7762@alvh.no-ip.org>
In-Reply-To: <1305910393-sup-7762@alvh.no-ip.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le 05/20/2011 06:53 PM, Alvaro Herrera a écrit :
> 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.
> 

Could be. Not sure it's that important.


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com