Re: Catalog Security WAS: Views, views, views: Summary

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, Andrew Dunstan <andrew(at)dunslane(dot)net>, andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Catalog Security WAS: Views, views, views: Summary
Date: 2005-05-14 13:50:09
Message-ID: 20050514135009.GA30902@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 14, 2005 at 08:55:17AM -0400, Stephen Frost wrote:
> * Christopher Kings-Lynne (chriskl(at)familyhealth(dot)com(dot)au) wrote:
> > >It bothers me a great deal that I can't control very easily what a given
> > >user can see when they connect over ODBC or via phppgadmin in terms of
> > >schemas, tables and columns. I fixed this in application code in
> > >phppgadmin but that's clearly insufficient since it doesn't do anything
> > >for the other access methods.
> >
> > Hackers - we get an email about information hiding in shared
> > postgresql/phppgadmin installations at least once a fortnight :)
>
> I agree with this- it needs to be dealt with and fixed already, once and
> for all.

Given that the newsysviews all base visibility on granted permissions,
would they do the job for you?
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2005-05-14 14:00:09 Re: Catalog Security WAS: Views, views, views: Summary
Previous Message Stephen Frost 2005-05-14 12:55:17 Re: Catalog Security WAS: Views, views, views: Summary