Skip site navigation (1) Skip section navigation (2)

Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs

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 (view raw or flat)
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. +

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-01-14 04:40:23
Subject: Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs
Previous:From: Tom LaneDate: 2010-01-14 04:35:27
Subject: Re: BUG #5275: validate_exec in port/exec.c only reads u/g/o, not ACLs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group