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

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: Catalog Security WAS: Views, views, views: Summary
Дата
Msg-id 20050514024737.GB30011@ns.snowman.net
обсуждение исходный текст
Ответ на Re: Catalog Security WAS: Views, views, views: Summary  (Russell Smith <mr-russ@pws.com.au>)
Ответы Re: Catalog Security WAS: Views, views, views: Summary  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Список pgsql-hackers
* Russell Smith (mr-russ@pws.com.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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Catalog Security WAS: Views, views, views: Summary
Следующее
От: Christopher Kings-Lynne
Дата:
Сообщение: Re: Catalog Security WAS: Views, views, views: Summary