Re: PF_NO_SIGSTOP (Was: PT_EXITKILL)

2012-11-08 Thread Amnon Shiloh
Hi Oleg, > Is this the only reason why this service keeps its original real-UID? > (see below) Allowing the user who invoked my service to send it signals is the main reason for keeping the original real-UID, but not the only one. > What if we introduce SA_NOSECURITY? So that if an application

PF_NO_SIGSTOP (Was: PT_EXITKILL)

2012-11-08 Thread Oleg Nesterov
On 11/08, Amnon Shiloh wrote: > > > > What I wish is that I could request (using "prctl" or whatever): > > > "If a non-privileged user sends me a SIGSTOP, then let it be converted > > > into...", > > > > I hope we won't do this ;) But I am not going to argue if you convince > > other people. > >

PF_NO_SIGSTOP (Was: PT_EXITKILL)

2012-11-08 Thread Oleg Nesterov
On 11/08, Amnon Shiloh wrote: What I wish is that I could request (using prctl or whatever): If a non-privileged user sends me a SIGSTOP, then let it be converted into..., I hope we won't do this ;) But I am not going to argue if you convince other people. To me it would be

Re: PF_NO_SIGSTOP (Was: PT_EXITKILL)

2012-11-08 Thread Amnon Shiloh
Hi Oleg, Is this the only reason why this service keeps its original real-UID? (see below) Allowing the user who invoked my service to send it signals is the main reason for keeping the original real-UID, but not the only one. What if we introduce SA_NOSECURITY? So that if an application