On Tue, Aug 31, 2004 at 01:33:30PM +0300, Nadav Har'El wrote: > On Tue, Aug 31, 2004, Nadav Har'El wrote about "Re: I'm not the process you think I > am": > > You can try doing this with Linux's little-known "capabilities" feature. > > This allows you to have any user id, but with some of root's capabilities, > > like binding any network address or writing any file (for example) > > magically turned on. For your protection, you can even enable some capabilties > > but not others. > > On second thought, while it's easy to have a root (uid 0) owned process > with lesser privelges (useful for enhanced security), it's less clear how > to use the "capabilities" mechanism to elevate the capabilities of a non- > root process. capsetp (controlling another process) might not be allowed > on standard kernels; And setuid et al. might clear all the capabilities > while changing the uid :(
That's actually solvable, since in my scenario, I have a parent process that's setuid 0, which can elevate the capabilities of the target process after making it setuid user. But see my other mail on why capabilities aren't a good solution at this stage. Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/
signature.asc
Description: Digital signature
