From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Random fork showing up in policy.
Date: Fri, 12 Feb 2010 10:17:51 -0500 [thread overview]
Message-ID: <4B75711F.5070908@redhat.com> (raw)
In-Reply-To: <1265980035.911.88.camel@gorn.columbia.tresys.com>
On 02/12/2010 08:07 AM, Christopher J. PeBenito wrote:
> On Thu, 2010-02-11 at 08:37 -0500, Daniel J Walsh wrote:
>> There has got to be something I am doing wrong. But on my blog someone asked about writing a program that does a fork and having SELinux block it.
>>
>> Where is the fork access coming from?
>
> Are you sure its not this:
>
> allow domain self:process { fork sigchld };
>
> in domain.te?
>
>> In the tmp dir I see this policy being compiled.
>>
>> # grep process.*fork fork.tmp
>> class process { fork transition sigchld sigkill sigstop signull signal ptrace getsched setsched getsession getpgid setpgid getcap setcap share getattr setexec setfscreate noatsecure siginh setrlimit rlimitinh dyntransition setcurrent execmem execstack execheap setkeycreate setsockcreate };
>> type_transition initrc_t fork_exec_t:process fork_t;
>> type_transition init_t fork_exec_t:process fork_t;
>> type_transition unconfined_t fork_exec_t:process fork_t;
>> neverallow fork_t self:process fork;
>>
>>
>> But if I install.
>>
>> # semodule -i fork.pp
>> libsepol.check_assertion_helper: neverallow violated by allow fork_t fork_t:process { fork };
>> libsemanage.semanage_expand_sandbox: Expand module failed
>> semodule: Failed!
>>
>> If I remove the neverallow line.
>>
>> # sesearch -A -s fork_t -p fork
>> Found 1 semantic av rules:
>> allow fork_t fork_t : process { fork sigchld } ;
>>
>> Something strange is going on.
>
Yes that is it.
Seems like a strange rule to have on domain. Might be better to move it to daemon rather then have it on domain.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-02-12 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 13:37 Random fork showing up in policy Daniel J Walsh
2010-02-12 13:07 ` Christopher J. PeBenito
2010-02-12 15:17 ` Daniel J Walsh [this message]
2010-02-12 16:01 ` {SPAM?} " Christopher J. PeBenito
2010-02-12 21:31 ` Daniel J Walsh
2010-02-16 14:19 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B75711F.5070908@redhat.com \
--to=dwalsh@redhat.com \
--cc=cpebenito@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.