🚀 go-pugleaf

In article <1992Jul22.134745.17309@newshost.lanl.gov>, jfowler@beta.lanl.gov (John C. Fowler) writes:
>In article <14htt0INNiep@hilbert.math.ksu.edu> tar@math.ksu.edu (Tim Ramsey) writes:
>>How do you get a complete list of files that are trusted by root, or by
>>programs that root trusts (that is, are setuid root)?
>
>To find out if a file is trusted, go to the man directories and grep the
>filename on everything, then read the associated man pages where the filename
>turned up (important files usually have their own man pages as well).
>
>To find setuid root files, use the "find" command.
>
>>Much easier to simply not have world-writable files owned by root.
>
>Agreed.  Much easier to simply not have world-writable files at all, unless
>you can come up with a real reason for needing them.  With UNIX supporting
>setuid and setgid programs, it's fairly easy to work around these days.
>
>But I still contend that there's nothing "special" about root owning a
>world-writable file that would allow a user to exploit it over anyone else
>owning the same file, other than getting around quotas.
An exception occurs to me in the case of /etc/utmp under SunOS 4.1.1 - the mode
this is set to by default is 666, hence it is world writeable.
If you reedit this with a simple C Program, you can make yourself invisible to
who commands etc. and also can evade certain accounting programs.

>
>-- 
>John C. Fowler, jfowler@lanl.gov
Jon Care, jonc@sc.plym.ac.uk.