Received: from ns.krot.org (ns.krot.org [193.212.103.165]) by postgresql.org (8.11.3/8.11.4) with SMTP id f9J1rQP03356 for ; Thu, 18 Oct 2001 21:53:30 -0400 (EDT) (envelope-from postgresql@envisity.com) Received: (qmail 30513 invoked by uid 67); 19 Oct 2001 01:51:18 -0000 Message-ID: <20011019015118.25128.qmail@ns.krot.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline MIME-Version: 1.0 From: "Aasmund Midttun Godal" To: pgsql-sql@postgresql.org Subject: Access to functions Date: Fri, 19 Oct 2001 01:51:18 GMT X-Mailer: Googley-Moogley Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by postgresql.org id f9J20RM05423 X-Archive-Number: 200110/269 X-Sequence-Number: 5222 There is currently no functionality to grant or deny access to functions. I believe anyone can run any function and the function is run as the user who runs it. This is also the case with views, which is odd, as the rest of the select statement is granted access to a table which the function in the view does not have access to. Functions triggered seem on the other handed to be 'trusted'. This can obviously be exploited. I have noticed a trusted field in the pg_proc and pg_language tables, can I use this somehow (I haven't got my hopes up as they are all 't' on pg_proc), ?? I looked through the todo, and albeit being a lot of new features in the grant section I cannot find any info regarding these issues. Sincerely, Aasmund. Aasmund Midttun Godal aasmund@godal.com - http://www.godal.com/ +47 40 45 20 46