--wxDdMuZNg1r63Hyj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Jul 15, 2003 at 12:40:57PM -0700, Bill Studenmund wrote:
> On Tue, 15 Jul 2003 ww@styx.org wrote:
>=20
> > On Tue, Jul 15, 2003 at 11:47:20AM -0700, Bill Studenmund wrote:
> > > On Mon, 14 Jul 2003, Greg A. Woods wrote:
> > >
> > > Since the program should (or can) know the path the file should have,=
 let
> > > it take care of remembering it. That way only the cases that need this
> > > bother with it.
> >
> > Not really -- file descriptors inherited from parent processes:
> > shell redirections and such.
>=20
> Yes, but come on, how many programs really really are going to want to
> unlink stdin or stdout? Close, yes, but unlink?

Some 31ee7 hAx0r group will surely find a way to, err, make use of=20
unlinking stdin/stdout, if they find a vulnerable networked program.

Seriously: think of passing some open descriptors to plug-ins , then letting
_them_ dispose of the file... although you could open, unlink, then call
the plugin, if it doesn't need the filename.


	-is
--=20
seal your e-mail: http://www.gnupg.org/

--wxDdMuZNg1r63Hyj
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE/FF3wPCRcZ/VMtk4RAqx/AJ0eR2MeqMCdxocaIcc0BBYWKSR/LACfSTlV
rHbHw/vlSa2QjvbjW0y4NAU=
=gKBi
-----END PGP SIGNATURE-----

--wxDdMuZNg1r63Hyj--