Re: Security problems with access(2)?

[Jordan DeLong]

in a project I'm currently working on I use the access(2) call when
going through a path for plugins to load.  For each : delim on the path
it does an access(2) to see if there is a file there, and then it
uses dlopen(3) to open the file as a share object, and responds
appropriatly to any errors it may recieve from the dlopen(3)
call.

I'd like to offer this as an example of a reasonable, and noninsecure
usage of access (please correct me if I'm wrong).  I'm not worried about
if the file is created after the access call: I'm just using the
access call to avoid having to do a dlopen() on every : delim
in the path.

Thoughts?

-- 
Jordan DeLong
[EMAIL PROTECTED]

PGP signature