| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Required permissions for data directory |
| Date: | 2004-10-12 19:09:42 |
| Message-ID: | 5560.1097608182@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> For 8.0 are we going to allow group modifications to the data
> directories for PostgreSQL? It is kind of silly that it must be 700.
Not in the least. There are many systems where users by default
are all in a "users" group, and so 770 isn't much safer than 777.
> I think we should allow at least 770. This allows you to have
> administrators with postgresql.conf editing rights without giving
> them the ability to su to postgresql.
Being able to edit postgresql.conf gives one the ability to become
postgres (hint: you can cause the backend to load a shlib of your
choosing, or even more trivially, adjust pg_hba.conf to let you in
as superuser), so the above distinction is unenforceable.
In short: no way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-12 19:14:13 | Re: Strange code in initdb |
| Previous Message | Joshua D. Drake | 2004-10-12 18:51:47 | Required permissions for data directory |