Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 04BCE9FBD59 for ; Wed, 9 May 2007 10:05:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 10307-09 for ; Wed, 9 May 2007 10:05:23 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by postgresql.org (Postfix) with ESMTP id 3F13F9FBE36 for ; Wed, 9 May 2007 10:05:23 -0300 (ADT) Received: by nz-out-0506.google.com with SMTP id s1so195095nze for ; Wed, 09 May 2007 06:05:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=DaFExGU7rAMOnMxxqNZxmBSvMaO8dbYZm6B/AJCvvgSmF7jSBRqqQhXPz5+Po2fMyHW2wVnvN7AC5QTQrE0FMFlimI8RzmPjeNvsDEETp5V7AIkFYtNy23DHeNVBleegt4NnEYw2aVxElXuA2cgWM9y3rO6zWmwIQoljMB+W8Ow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=orI+9bZyiPfNg62uIsUyyvVHevwQaBnpe3oc8su3rtzzJLqlbt+h+i70MH30HUcb2m7scjbHLMcPB5Ll3lTlq5Oip4qHmf7XbV94zK7yFY4PFFhA/UVk/swda2xZAwYwp8i73f/FhNEm80C/72VnsHU5VNtT6WqKXAjwnLznEso= Received: by 10.115.60.1 with SMTP id n1mr182404wak.1178715921384; Wed, 09 May 2007 06:05:21 -0700 (PDT) Received: by 10.115.72.5 with HTTP; Wed, 9 May 2007 06:05:21 -0700 (PDT) Message-ID: <48d0cacb0705090605i4c1c2107s2186c52468e07d46@mail.gmail.com> Date: Wed, 9 May 2007 10:05:21 -0300 From: "Daniel Cristian Cruz" To: pgsql-admin Subject: Revoking usage of pg_catalog MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_130501_22049601.1178715921332" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/60 X-Sequence-Number: 25380 ------=_Part_130501_22049601.1178715921332 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi there! Is it possible to revoke usage of pg_catalog for a specific user? The reason is to secure PostgreSQL. If a user can connect to a database, it could query pg_class, pg_attribute, pg_proc search for specific tables and if using dblink, even database passwords... I just made a test, revoking usage of pg_catalog from PUBLIC, but tables are still available through "SELECT * FROM pg_class", but not through "SELECT * FROM pg_catalog.pg_class". I found in manual, where it says pg_catalog is searched before any schema on search_path... If schema pg_catalog became blocked, PostgreSQL could be used? Could it be possible to made queries on allowed schemas and tables? This could be an item for the wishlist? Kind regards, -- Daniel Cristian Cruz ------=_Part_130501_22049601.1178715921332 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi there!

Is it possible to revoke usage of pg_catalog for a specific user?

The reason is to secure PostgreSQL. If a user can connect to a database, it could query pg_class, pg_attribute, pg_proc search for specific tables and if using dblink, even database passwords...

I just made a test, revoking usage of pg_catalog from PUBLIC, but tables are still available through "SELECT * FROM pg_class", but not through "SELECT * FROM pg_catalog.pg_class". I found in manual, where it says pg_catalog is searched before any schema on search_path...

If schema pg_catalog became blocked, PostgreSQL could be used? Could it be possible to made queries on allowed schemas and tables? This could be an item for the wishlist?

Kind regards,
--
Daniel Cristian Cruz ------=_Part_130501_22049601.1178715921332--