From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Russell Smith <mr-russ(at)pws(dot)com(dot)au> |
Cc: | 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 02:47:38 |
Message-ID: | 20050514024737.GB30011@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Russell Smith (mr-russ(at)pws(dot)com(dot)au) wrote:
> Tom mentioned that he had not had these security concerns raised before. From
> my point of view I just have no idea about the level of information offered
> to any given user and am scared to run PostgreSQL in an ISP shared
> environment because of it. I am sure I can secure people from connecting to
> a db by refusing them access in pg_hba.conf. But I'm unsure of exactly what
> that buys me, and what is doesn't.
It's certainly also a concern of mine that any given use can see every
table in the database. I see that as a definite problem and just
assumed it was already on the radar and something that was planned to be
fixed. It astounds me that the claim is that such security is
impossible.
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.
I'd certainly really like to see this fixed. It would raise my comfort
level a great deal wrt allowing people to use ODBC and psql directly.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-14 02:48:13 | Re: Permissions not removed when group dropped |
Previous Message | Alvaro Herrera | 2005-05-14 02:39:38 | Re: Catalog Security WAS: Views, views, views: Summary |