|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Re[2]: snooper watchers
Karl Strickland (karl
bagpuss.demon.co.uk)Fri, 3 Mar 1995 21:21:40 +0000 (GMT)
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Matthew Bontoft: "RE: set group id on directories (fwd)"
- Previous message: Timothy Newsham: "Re: Re[2]: snooper watchers"
- In reply to: Timothy Newsham: "Re: Re[2]: snooper watchers"
- Next in thread: Reto Lichtensteiger: "Re: rebooting (was Snooper watchers)"
> > > Yep hacking suser()'s idea of root's uid is an example of a trivial > > modification, thats trivial to do. What the other guy was on about - loading > > new (non-loadable, obviously) modules into a running kernel is distinctly > > non-trivial in comparison; hence my point that it depends on the mods you're > > making. Thats whay Im interested to hear the two ways. > > Hacking the system to have another idea of what a suser() is is easy enough. > What is not easy is finding all the userland programs that depend on > a particular definition of what is and what isnt a super user. For example > if you changed superuser to uid 31337 then all of the sudden sendmail > and nfs bugs let you become root without going through another account > first. yes but with respect, suser() isnt really the point is it. -- ------------------------------------------+----------------------------------- Mailed using ELM on FreeBSD | Karl Strickland PGP 2.3a Public Key Available. | Internet: karlbagpuss.demon.co.uk |
- Next message: Matthew Bontoft: "RE: set group id on directories (fwd)"
- Previous message: Timothy Newsham: "Re: Re[2]: snooper watchers"
- In reply to: Timothy Newsham: "Re: Re[2]: snooper watchers"
- Next in thread: Reto Lichtensteiger: "Re: rebooting (was Snooper watchers)"