On Sep 17, 2005, at 18:31:33, D. Hazelton wrote:
That, and my point remains that the kernel should know absolutely
nothing about how to execute a text file - the kernel should return
an error to the extent of "I don't know what to do with this file"
to the shell that tries to execute it, and the shell can then check
for the sh_bang. I do admit that this change would break a lot of
existing code, so I'll leave the argument to the experts.
No, that would not work at all. We have a very nice system to allow
set-uid scripts (Specifically, I like my nice secure taint-mode set-
uid perl scripts). If you did this, they would break completely, not
to mention _add_ all sorts of unsolvable race conditions to the few
ways of working around such a lack of SUID scripts. Also, it means
that I can't just "mv /sbin/init /sbin/init.real ; vim /sbin/init" to
do a simple wrapper around the init program, I would need to write a
compiled C program to do all sorts of fragile hackish things like
calling a script /sbin/init.sh.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the
other way is to make it so complicated that there are no obvious
deficiencies. The first method is far more difficult.
-- C.A.R. Hoare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |