On Fri, Jun 02, 2006 at 09:27:28AM +0100, Darren J Moffat wrote: > Thats exactly the type of case I'm looking at. > > In many ways this isn't actually any different to having the ability to > drop proc_fork and proc_exec. Yes there are library calls that fork and > exec !
I know. I'm still a bit uneasy, particularly about the basic privileges for IPC -- the more likely a facility is to be used deep in some library some time in the future, the more likely it is that providing a basic privilege for it might lead to breakage. The problem isn't existing libraries -- it's future changes to existing libraries. I'd hate to be unable to change some library to use IPC because some application that depends on that library drops basic IPC privs. Could we have an alarm privset? Use of any privileges in it would cause an audit event/alarm of some sort? _______________________________________________ networking-discuss mailing list [email protected]
