[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cfexecd and chmod($input_dir)
From: |
Darrell Fuhriman |
Subject: |
Re: cfexecd and chmod($input_dir) |
Date: |
Sat, 05 Jun 2004 18:06:33 -0700 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) |
Mark.Burgess@iu.hio.no writes:
> The directory must be trusted. Why do you care?
Who's the right one to decide what's trusted, the user, or the author of
the software? In my opinion, it's the user.
Here's one reason you might care: you want your sysadmins to be
able to edit the files in inputs without being root. Maybe it's
not a good idea, but that's for the end-user to decide.
If you want to enforce that sort of policy, it should be a
configuration option, not something hard-coded -- at the very
least the user should have the option of disabling it.
Darrell
- cfexecd and chmod($input_dir), Will Lowe, 2004/06/04
- Re: cfexecd and chmod($input_dir), Mark . Burgess, 2004/06/05
- Re: cfexecd and chmod($input_dir),
Darrell Fuhriman <=
- Re: cfexecd and chmod($input_dir), Chip Seraphine, 2004/06/08
- Re: cfexecd and chmod($input_dir), Will Lowe, 2004/06/08
- Re: cfexecd and chmod($input_dir), Mark . Burgess, 2004/06/08
- Re: cfexecd and chmod($input_dir), Luke A. Kanies, 2004/06/08
- Re: cfexecd and chmod($input_dir), Mark . Burgess, 2004/06/09
- Re: cfexecd and chmod($input_dir), Chip Seraphine, 2004/06/09
- Re: cfexecd and chmod($input_dir), Brendan Strejcek, 2004/06/09