X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8DA1554580 for ; Fri, 4 Mar 2005 17:01:05 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 22692-06 for ; Fri, 4 Mar 2005 17:01:03 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 02B0252A9A for ; Fri, 4 Mar 2005 17:01:02 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id j24H0vZd005615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 4 Mar 2005 10:01:00 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.3/8.13.3) with ESMTP id j24H0vmj044300 for ; Fri, 4 Mar 2005 10:00:57 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.3/8.13.3/Submit) id j24H0vcB044299 for pgsql-admin@postgresql.org; Fri, 4 Mar 2005 10:00:57 -0700 (MST) (envelope-from mfuhr) Date: Fri, 4 Mar 2005 10:00:57 -0700 From: Michael Fuhr To: pgsql-admin@postgresql.org Subject: Re: How to deny remote backups ? Message-ID: <20050304170057.GA44195@winnie.fuhr.org> References: <4208B84C0001250D@resmta04.ono.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4208B84C0001250D@resmta04.ono.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/45 X-Sequence-Number: 16543 On Fri, Mar 04, 2005 at 05:33:02PM +0100, juanmime@ono.com wrote: > OK. but I think that an aproximation to the solution or a half solution could > be deny the user consulting the system database catalog or (pg_tables). In > that case, the user is not able to know the name of the tables inside the > db, and therefore he does not know which are the tables to dump. I think > also, that pg_dump could fail at this scenario. Users presumably already know about the tables they're allowed to SELECT from -- otherwise how would they know to query them? So in that case, protecting the system catalogs wouldn't help. And for the tables that users don't know about but could discover through the system catalogs, if the users don't have SELECT privileges then they won't be able to dump those tables anyway. What problem are you really trying to solve? If you want to hide the fact that certain tables exist, then maybe you could put them in a separate database and use a mechanism involving dblink with views and/or functions to control access to them. -- Michael Fuhr http://www.fuhr.org/~mfuhr/