On Mon, 11 Sep 2000, Igmar Palsenberg wrote:
> > Correct me if I'm wrong, but I believe that all non-TOS
> > unices have behaved this way since the 70s.
>
> I see no reason why it shouldn't behave this way. Root can do su - user
> and screw up the file that way.
>
> Users with UID 0 are capable
> Correct me if I'm wrong, but I believe that all non-TOS
> unices have behaved this way since the 70s.
I see no reason why it shouldn't behave this way. Root can do su - user
and screw up the file that way.
Users with UID 0 are capable of doing about anything possible.
Igmar
-
To un
> [root@pepsi /tmp]# su adam
> [adam@pepsi /tmp]$ touch blah
> [adam@pepsi /tmp]$ chmod -w blah
> [adam@pepsi /tmp]$ echo hi > blah
> bash2: blah: Permission denied
> [adam@pepsi /tmp]$ exit
> exit
> [root@pepsi /tmp]# echo hi > blah
> [root@pepsi /tmp]# ls -l blah
> -r--r--r--1 adam a
On Fri, 8 Sep 2000, Adam wrote:
> Hmm can someone remind me what (if) is the reason root is not bound by
> write permissions?
Because linux is not a trusted operating system. On linux,
root = uid 0 = superuser.
> [root@pepsi /tmp]# su adam
> [adam@pepsi /tmp]$ touch blah
> [adam@pepsi /tmp
Hmm can someone remind me what (if) is the reason root is not bound by
write permissions?
[root@pepsi /tmp]# su adam
[adam@pepsi /tmp]$ touch blah
[adam@pepsi /tmp]$ chmod -w blah
[adam@pepsi /tmp]$ echo hi > blah
bash2: blah: Permission denied
[adam@pepsi /tmp]$ exit
exit
[root@pepsi /tmp]#
5 matches
Mail list logo