home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.internals
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!agate!stanford.edu!leland.Stanford.EDU!dkeisen
- From: dkeisen@leland.Stanford.EDU (Dave Eisen)
- Subject: Re: Changing the owner of a process
- Message-ID: <1992Nov17.231339.29632@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: Sequoia Peripherals, Inc.
- References: <1992Nov5.152833.27744@dale.ksc.nasa.gov> <1992Nov17.142837.21252@dale.ksc.nasa.gov> <Uf2Hn7G00WB4MtP4gQ@andrew.cmu.edu>
- Date: Tue, 17 Nov 92 23:13:39 GMT
- Lines: 27
-
- In article <Uf2Hn7G00WB4MtP4gQ@andrew.cmu.edu> Tod McQuillin <tm8t+@andrew.cmu.edu> writes:
- >> What I was looking for was something along the lines of how to change the
- >> effective user id of a process who's source I may not be able to modify, by
- >> some other means, e.g. from another process. Many suggested writing a device
- >> driver or system call to do this. Here is one answer along those lines.
-
- >Yeah, but you don't need a device driver to do that. Just use
- >/dev/kmem, /vmunix, and nlist(3).
-
- True. But....
-
- There is some risk involved in fiddling with /dev/kmem this way. It
- is quite possible for the process in question to disappear between
- the time you read /dev/kmem to find the proc table slot and the
- time you write the new value back. This could cause massive security
- problems if an unrelated process has started and was assigned this
- slot.
-
- I'd probably do this using /dev/kmem if I were to do it. But using a
- driver is definitely safer.
-
-
- --
- Dave Eisen Sequoia Peripherals: (415) 967-5644
- dkeisen@leland.Stanford.EDU Home: (415) 321-5154
- There's something in my library to offend everybody.
- --- Washington Coalition Against Censorship
-