From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Hallstrom <philip(at)adhesivemedia(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Explain auth/access/priv system?? |
Date: | 2000-05-23 22:51:35 |
Message-ID: | 4560.959122295@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Philip Hallstrom <philip(at)adhesivemedia(dot)com> writes:
> Got it. Thanks again. So really that last entry in pg_hba.conf (the
> "local...all...trusted") is dangerous... can any user who can connect to a
> database also drop tables?
No, because there is table-level protection. I think only the table
owner (creator) or the superuser can drop a table. Other access rights
for a table are controlled by GRANT/REVOKE --- see the doc pages for
those commands for more info. IIRC, the default is no access...
"local...all...trusted" is not a good idea on a machine where you don't
trust the other users, but that's because someone else can pretend to
be any authorized user (even the superuser!). I'd at least suggest
"ident" authentication in that situation, maybe "password" if the need
to enter passwords isn't too much of a PITA. You could also use
Kerberos if you have that installed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-05-23 23:55:10 | Re: [GENERAL] Re: Postgresql OO Patch |
Previous Message | Philip Hallstrom | 2000-05-23 22:28:25 | Re: Explain auth/access/priv system?? |