Re: [PATCH 0/3] New system call, unshare

2005-09-07 Thread Janak Desai
Al Viro wrote: On Wed, Aug 10, 2005 at 04:08:31PM +0200, Florian Weimer wrote: * Janak Desai: With unshare, namespace setup can be done using PAM session management functions without patching individual commands. I don't think it's a good idea to use security-critical code well without its

Re: [PATCH 0/3] New system call, unshare

2005-08-22 Thread Al Viro
On Wed, Aug 10, 2005 at 04:08:31PM +0200, Florian Weimer wrote: > * Janak Desai: > > > With unshare, namespace setup can be done using PAM session > > management functions without patching individual commands. > > I don't think it's a good idea to use security-critical code well > without its ori

Re: [PATCH 0/3] New system call, unshare

2005-08-10 Thread Janak Desai
[EMAIL PROTECTED] wrote: Quoting Florian Weimer ([EMAIL PROTECTED]): * Janak Desai: With unshare, namespace setup can be done using PAM session management functions without patching individual commands. I don't think it's a good idea to use security-critical code well Note that this pat

Re: [PATCH 0/3] New system call, unshare

2005-08-10 Thread serue
Quoting Florian Weimer ([EMAIL PROTECTED]): > * Janak Desai: > > > With unshare, namespace setup can be done using PAM session > > management functions without patching individual commands. > > I don't think it's a good idea to use security-critical code well Note that this patch is not removing

Re: [PATCH 0/3] New system call, unshare

2005-08-10 Thread Florian Weimer
* Janak Desai: > With unshare, namespace setup can be done using PAM session > management functions without patching individual commands. I don't think it's a good idea to use security-critical code well without its original specification. Clearly the current situation sucks, but this is mainly