From: Daniel J Walsh <dwalsh@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: is any use of runcon by arbitrary users valid when enforcing?
Date: Sun, 07 Oct 2007 08:09:49 -0400 [thread overview]
Message-ID: <4708CC8D.5030803@redhat.com> (raw)
In-Reply-To: <87fy0n9zn3.fsf@rho.meyering.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Meyering wrote:
> In a simple test of runcon for coreutils test suite, I used the following,
> but see that it's failing in an enforcing F8t3 environment:
> [from coreutils/tests/misc/runcon]
>
> ...
> cat <<\EOF > exp || framework_failure
> runcon: runcon may be used only on a SELinux kernel
> EOF
>
> fail=0
>
> # This test works even on systems without SELinux.
> # On such a system it fails with the above diagnostic, which is fine.
> # Before the no-reorder change, it would have failed with a diagnostic
> # about -j being an invalid option.
> runcon -t unconfined_t true -j 2> out && : > exp
>
> compare out exp || fail=1
>
> (exit $fail); exit $fail
>
> Is there any similar use of runcon that can be expected to succeed?
>
> --
> 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.
This would only work on a system that allowed the running domain to
transition to unconfined_t. If this is an automated test, then it is
probably running in initrc_t. So for your test environment I would load
a policy module that would allow the transition from initrc_t to
unconfined_t or any other transitions that you need. This is what the
internel test suites at Red Hat do, to eliminate avc's caused by the
test environment.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHCMyNrlYvE4MpobMRAis2AKCXrQq5c2bi1qUlRezIKKTL5F/vtwCdGaAi
88T9O+oAHVsW0dOnnI1KT0A=
=yqe9
-----END PGP SIGNATURE-----
--
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:[~2009-09-28 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 7:01 is any use of runcon by arbitrary users valid when enforcing? Jim Meyering
2007-10-07 12:09 ` Daniel J Walsh [this message]
2007-10-09 13:17 ` Stephen Smalley
2007-10-09 16:01 ` Jim Meyering
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=4708CC8D.5030803@redhat.com \
--to=dwalsh@redhat.com \
--cc=jim@meyering.net \
--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.