Re: [PATCH 1/3] exporting capability code/name pairs (try #3)

2008-02-05 Thread Serge E. Hallyn
Quoting Kohei KaiGai ([EMAIL PROTECTED]): > Serge E. Hallyn wrote: >> Quoting Kohei KaiGai ([EMAIL PROTECTED]): > All that being said, the friendliness factor of this is somewhat > undeniable, and so I can see why folk might want it in the kernel > anyway. If so, would it possible to mo

Re: [PATCH 1/3] exporting capability code/name pairs (try #3)

2008-02-05 Thread Kohei KaiGai
Serge E. Hallyn wrote: Quoting Kohei KaiGai ([EMAIL PROTECTED]): All that being said, the friendliness factor of this is somewhat undeniable, and so I can see why folk might want it in the kernel anyway. If so, would it possible to move this code into security/capability.c and not in the main ke

Re: [PATCH 1/3] exporting capability code/name pairs (try #3)

2008-02-04 Thread Serge E. Hallyn
Quoting Kohei KaiGai ([EMAIL PROTECTED]): > >> All that being said, the friendliness factor of this is somewhat > >> undeniable, and so I can see why folk might want it in the kernel > >> anyway. If so, would it possible to move this code into > >> security/capability.c and not in the main kernel p

Re: [PATCH 1/3] exporting capability code/name pairs (try #3)

2008-01-31 Thread Kohei KaiGai
>> All that being said, the friendliness factor of this is somewhat >> undeniable, and so I can see why folk might want it in the kernel >> anyway. If so, would it possible to move this code into >> security/capability.c and not in the main kernel per-se - protected with >> a configuration option?