home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!cs.utexas.edu!torn!utgpu!utstat!rafal
- From: rafal@utstat.uucp (Rafal Kustra (summer student))
- Subject: Suid/sgid
- Message-ID: <1992Aug25.230907.10073@utstat.uucp>
- Organization: University of Toronto, Dept. of Statistics
- Date: Tue, 25 Aug 1992 23:09:07 GMT
- Lines: 31
-
- Perhaps this should be posted to other group
- but I only have time to read this one + some local
- ones ;).
- OK, here is the beef.
- Either I don't understand the concept of suid/sgid
- (**very** possible) or there is something wrong.
- Say root creates a script like follows:
- cat $*
- and sets it suid.
- Now normal user could cut any r--.....
- file with it, right? Well I (as normal user) get usuall
- cat:foo not owner
- where foo belongs to root and has r-------- perms.
- Also root's script with:
- echo "user ID" $UID
- echo "effective user ID" $EUID
- reports calling user's ID twice even when set sgid and x
- for others.
- Also my elm with root:mail ownership would't work right
- even with suid. I had to sgid it too.
- (It wouldn't be able to create folder in /usr/spool/mail
- which is also root:mail).
- On the other hand pcomm with suid set enables anyone to
- become root just by jumping to subshell.
- Any ideas?
- (I'm using 0.96cpl2 w/o SCSI support).
- --
- /|| Numbers exist only in our minds. There is no physical entity that
- ||_is_ number 1. If there were, 1 would be in a place of honor in
- || some great museum of science, and past it would file a steady
- ==== stream of mathematicians gazing at 1 in wonder and awe.
-