Permissions/security on pg_* tables?

From: dkelson-list-pgsql-hackers(at)inconnect(dot)com
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Permissions/security on pg_* tables?
Date: 1998-11-17 01:46:00
Message-ID: Pine.LNX.4.02A.9811161843530.424-100000@brookie.inconnect.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Another one...

---------- Forwarded message ----------
Date: Sun, 15 Nov 1998 23:08:27 -0700 (MST)
From: Dax Kelson <dkelson-list-pgsql-admin(at)inconnect(dot)com>
Cc: pgsql-admin(at)postgreSQL(dot)org
Subject: [ADMIN] Permissions/security on pg_* tables?

Is it normal/desirable for any user to be able to select (haven't tried
insert/update) in the pg_* tables?

Is it possible to GRANT/REVOKE on the pg_* tables? It seems it is. How
can you see the permissions if \z doesn't work on the pg_* tables?

Given a multi-user environment were each user (and the sysadmin) values
security quite highly, what is the best way to secure PostgreSQL as
tightly as possible (not just looking at data in tables, but general
snooping around)?

In pg_hba.conf under "host" the second parameter is "dbname". Is it
possible to have a list of databases?

Ie:

host db1,db2,db3 10.0.0.3 255.255.255.255 crypt

Or is it limited to (all|samename|onedbname)?

Thanks for your help,
Dax Kelson
Internet Connect, Inc.

Browse pgsql-hackers by date

  From Date Subject
Next Message David N. Cicalo 1998-11-17 02:36:30 Subscribe
Previous Message dkelson-list-pgsql-hackers 1998-11-17 01:45:11 New to PostgreSQL, is this a DoS?