init and sigchld
What is the benefit in denying sigchld access to init?
How can a process do harm by sending sigchld to the init process?
I am thinking of doing the following:
allow domain init_t:signal sigchld;
Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 7 lines · Russell Coker
What is the benefit in denying sigchld access to init?
How can a process do harm by sending sigchld to the init process?
I am thinking of doing the following:
allow domain init_t:signal sigchld;
This rule used to exist in every.te, and was then moved into general_domain_access() in global_macros.te. I suppose we could revive every.te and put a few rules like this one into it.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 5 lines · Stephen Smalley
Quoted 4 lines · Russell Coker
What is the benefit in denying sigchld access to init?
How can a process do harm by sending sigchld to the init process?
Quoted 7 lines
Quoted 3 lines
I am thinking of doing the following:
allow domain init_t:signal sigchld;
This rule used to exist in every.te, and was then moved into
general_domain_access()in global_macros.te. I suppose we could revive every.te and put a few rules like this one into it.
OK. I've created an every.te file in my tree with this rule, and removed every instance of
allow ... init_t:process sigchld;
Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 3 lines · Russell Coker
OK. I've created an every.te file in my tree with this rule, and removed every instance of
allow ... init_t:process sigchld;
Actually, I suppose that we could just place this rule into init.te.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 6 lines · Stephen Smalley
Quoted 3 lines · Russell Coker
OK. I've created an every.te file in my tree with this rule, and removed every instance of
allow ... init_t:process sigchld;Actually, I suppose that we could just place this rule into init.te.
Makes sense to me. I've done that in my tree now.
Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.