[133] in linux-security and linux-alert archive
Re: "Find all the SUID programs." Fine. So which *should* be SUID?
daemon@ATHENA.MIT.EDU (Panzer Boy)
Mon Mar 13 00:58:09 1995
To: linux-security@tarsier.cv.nrao.edu
From: panzer@dhp.com (Panzer Boy)
Date: 12 Mar 1995 22:54:32 -0500
Reply-To: linux-security@tarsier.cv.nrao.edu
Geoffrey Bennett (geoffrey@tafe.sa.edu.au) wrote:
: > *** /bin/login doesn't need to suid root, as it should for the most part
: > only be called by root owned procs. ping for icmp. passwd stuff for
: > access to restricted shells.
: /bin/login should be suid root, in case someone wants to exec login,
: I thought?
Why are people execing login? In most cases you do not need this.
: No, inetd.conf specifies which user each server should be run as.
Ok, ok, grep "root" /etc/inetd.conf will show you what is being run as
root. :) Most things you are worried about are run as root. At the same
time you should make sure that things like finger, and other
non-privilege needing programs, aren't being run as root.
--
-Matt (panzer@dhp.com) DI-1-9026
"That which can never be enforced should not be prohibited."
--
[Mod: This topic is starting to veer away from Linux-specific security
into the realm of general UNIX security/administration. Let's try to
stay as Linux-specific as we can, as that's the main purpose for these
lists. Thanks. --Jeff]
