From: Michael Fuhr <mike@fuhr.org>
To: pgsql-admin@postgresql.org
Subject: Re: How to deny remote backups ?
Date: Fri, 4 Mar 2005 10:00:57 -0700
Message-ID: <20050304170057.GA44195@winnie.fuhr.org> (raw)
In-Reply-To: <4208B84C0001250D@resmta04.ono.com>
References: <4208B84C0001250D@resmta04.ono.com>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mike@fuhr.org
Subject: Re: How to deny remote backups ?
In-Reply-To: <20050304170057.GA44195@winnie.fuhr.org>
References: <4208B84C0001250D@resmta04.ono.com> <20050304170057.GA44195@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox