Date: Sun, 1 Apr 2001 14:33:48 -0700 From: Jordan DeLong <fracture@allusion.net> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Security problems with access(2)? Message-ID: <20010401143348.A74357@cx420564-b.tucson1.az.home.com> In-Reply-To: <nospam-986073263.85140@maxim.gbch.net>; from gjb@gbch.net on Sun, Apr 01, 2001 at 07:14:23AM %2B1000 References: <Pine.NEB.3.96L.1010331131056.40815F-100000@fledge.watson.org> <3AC644B1.1BB56BB3@iowna.com> <nospam-986073263.85140@maxim.gbch.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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? --=20 Jordan DeLong fracture@allusion.net --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjrHnrwACgkQDrrilS51AZ/8swCgzzbX0VYUToBR8O0KnR+yOdLY yXwAn0XpiSrJQEFA7oMH+GEHTyAqzT4N =wd8M -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010401143348.A74357>