Обсуждение: system catalog permissions

All;


We have a client which is segmenting their multi-tenant cluster 
(PostgreSQL 9.6) by schema, however if one of their clients connects via 
pgadmin they see ALL schemas, even the ones they don't have access to 
read. I assume pgadmin is pulling the list from the system catalogs.


What's the right/best practice approach? revoke all from public on 
specific system catalog tables? Which tables?


Thanks in advance

On 02/26/2018 03:11 PM, PropAAS DBA wrote:
> All;
>
>
> We have a client which is segmenting their multi-tenant cluster 
> (PostgreSQL 9.6) by schema, however if one of their clients connects 
> via pgadmin they see ALL schemas, even the ones they don't have access 
> to read. I assume pgadmin is pulling the list from the system catalogs.
>
>
> What's the right/best practice approach? revoke all from public on 
> specific system catalog tables? Which tables?

AFAIK, you can not hide the list of schemas but you can prevent people 
from entering them.


JD

>
>
> Thanks in advance
>
>

-- 
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc

PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
*****     Unless otherwise stated, opinions are my own.   *****

PropAAS DBA <dba@propaas.com> writes:
> We have a client which is segmenting their multi-tenant cluster 
> (PostgreSQL 9.6) by schema, however if one of their clients connects via 
> pgadmin they see ALL schemas, even the ones they don't have access to 
> read. I assume pgadmin is pulling the list from the system catalogs.

> What's the right/best practice approach? revoke all from public on 
> specific system catalog tables? Which tables?

Messing with the system catalog permissions is likely to break stuff
you'd rather not break.

PG generally doesn't assume that anything in the system catalogs is
sensitive.  If you don't want user A looking at user B's catalog
entries, give them separate databases, not just separate schemas.

            regards, tom lane

On 02/26/2018 03:47 PM, Tom Lane wrote:
> PropAAS DBA <dba@propaas.com> writes:
>> We have a client which is segmenting their multi-tenant cluster
>> (PostgreSQL 9.6) by schema, however if one of their clients connects via
>> pgadmin they see ALL schemas, even the ones they don't have access to
>> read.
> PG generally doesn't assume that anything in the system catalogs is
> sensitive.  If you don't want user A looking at user B's catalog
> entries, give them separate databases, not just separate schemas.

I'm sure this is what you meant, but you need to give them separate 
*clusters*, right? Even with separate databases you can still get a list 
of the other databases and other roles in the cluster. I would actually 
love to be mistaken but when I looked at it a year or two ago I couldn't 
find a way to lock that down (without breaking a lot of tools anyway).

Thanks!

-- 
Paul              ~{:-)
pj@illuminatedcomputing.com