| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | James Bellinger <jfb(at)zer7(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs |
| Date: | 2010-01-14 04:37:30 |
| Message-ID: | 201001140437.o0E4bUr10647@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I think access's reputation as something to avoid caused us not to look
> > at it. My old BSD manual says about access():
>
> > CAVEAT
> > The access() function should be used rarely, if ever. Specifically,
> > access() should never be used by any program whose user real and effec-
> > tive IDs, or group real and effective IDs, differ.
>
> But we force those to be the same in main.c. Anyway there are several
> other uses of access() in the code ...
Yea, I am not saying the text is right, but rather why it was not
considered for use in that case.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-14 04:40:23 | Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs |
| Previous Message | Tom Lane | 2010-01-14 04:35:27 | Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs |