Received: from mail4.zotnet.com (216-99-218-131.dsl.aracnet.com [216.99.218.131]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7P4gIf33558 for ; Sat, 25 Aug 2001 00:42:19 -0400 (EDT) (envelope-from zot@zotconsulting.com) Received: from zotconsulting.com (216-99-218-134.dsl.aracnet.com [216.99.218.134]) by mail4.zotnet.com (Postfix) with ESMTP id 4342F13599; Fri, 24 Aug 2001 21:33:02 -0700 (PDT) Message-ID: <3B872CA4.C888A771@zotconsulting.com> Date: Fri, 24 Aug 2001 21:42:12 -0700 From: "Zot O'Connor" X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Sawtell Cc: "pgsql-sql@postgresql.org" Subject: Re: Execute permsissions on fuctions References: <3B8550E9.3BC47EA7@zotconsulting.com> <20010824051425.22A6C1FA01E@deborah.paradise.net.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/309 X-Sequence-Number: 4556 Christopher Sawtell wrote: > > On Fri, 24 Aug 2001 06:52, Zot O'Connor wrote: > > Other SQL servers have the concept of stored procedures having different > > permissions. > > > > For instance a procedure that can update a table. > > > > Since a web site typically connects as the webuser (or equiv postgres > > user), I do not want to offer update to the webuser. > > > > The way I have done this elsewhere is to create a stored procedure that > > could update the table, and allow the webuser to update the table. The > > procedure had perms of a user who could update the table, but the > > webuser could not. > > > > How can I do this in Postgres? > > By not GRANTing the webuser write permission to the tables in question. I guess I should have been more clear. I want the webuser to be able to upadte the table VIA the function, and but not directly. Currently this does not work, since CREATE FUNCTION acts as any old function: zot=# CREATE TABLE testperms (id int4); CREATE zot=# CREATE FUNCTION effect_testperms (int4) RETURNS int4 AS 'INSERT INTO testperms (id) VALUES ($1); RETURN 1;' LANGUAGE 'sql'; SELECT effect_testperms(1); effect_testperms ------------------ 1 (1 row) zot=# \connect - nobody You are now connected as new user nobody. zot=> select * from testperms; ERROR: testperms: Permission denied. zot=> SELECT effect_testperms(2); ERROR: testperms: Permission denied. zot=> So it appears that FUCNTION effect_testperms() is taking on the perms of the user calling it. So it may be a generic issue with Postgres that other DBMS's effectively run the stored procedure as SUID-like, in that it takes on the perms of the owner of the procedure, not the user calling the procedure. -- Zot O'Connor http://www.ZotConsulting.com http://www.WhiteKnightHackers.com