From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <selinux@tycho.nsa.gov>, Eric Paris <eparis@redhat.com>,
James Morris <jmorris@redhat.com>
Subject: Re: I am trying to build an MLS livecd.
Date: Tue, 04 May 2010 14:18:26 -0400 [thread overview]
Message-ID: <4BE064F2.3060505@redhat.com> (raw)
In-Reply-To: <1272991523.30175.142.camel@moss-pluto.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/04/2010 12:45 PM, Stephen Smalley wrote:
> On Tue, 2010-05-04 at 12:34 -0400, Daniel J Walsh wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> But for some reason. Setfiles is not writing the correct labels to the
>> livecd, iff the label includes a range with a level not supported on the
>> host machine.
>>
>> grep s15 /tmp/mls.log
>> sbin/setfiles: /home matched by
>> system_u:object_r:home_root_t:s0-s15:c0.c1023
>> /sbin/setfiles: /home/liveadmin matched by
>> staff_u:object_r:user_home_dir_t:s0-s15:c0.c1023
>> /sbin/setfiles: /home/liveuser matched by
>> privuser_u:object_r:user_home_dir_t:s0-s15:c0.c1023
>>
>> When I boot the livecd these are all labeled as
>> unconfined_u:object_r:TYPE:s0.
>>
>> Any idea why this would happen?
>>
>> Of course these labels are invalid, so the MLS livecd is broken.
>
> Does the same problem occur if the type is undefined in the host policy?
> IOW, is this a problem with undefined contexts in general or specific to
> the MLS field?
>
> What output do you get if you run setfiles with -vv?
>
> Could mcstransd be incorrectly mapping the range to s0?
>
I attached the actuall output. Problem is it takes 1/2 hour to get back
to this state.
mcstransd would not be running in the environment. livecd has a hacked
out environment that thinks it is running SELinux in enforcing mode.
/selinux is a big hack and does nothing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkvgZPIACgkQrlYvE4MpobPlyACfc7WBoHliuHsT3TYU4rJ6Wetk
nigAoI7yzh37a0qEwr6+4PqbIeALO5Xw
=nYnC
-----END PGP SIGNATURE-----
[-- Attachment #2: out --]
[-- Type: text/plain, Size: 232 bytes --]
# file: home/
security.selinux="system_u:object_r:home_root_t:s0
# file: home/liveuser/
security.selinux="unconfined_u:object_r:user_home_dir_t:s0
# file: home/liveuser/
security.selinux="unconfined_u:object_r:user_home_dir_t:s0
[-- Attachment #3: out.sig --]
[-- Type: application/pgp-signature, Size: 72 bytes --]
next prev parent reply other threads:[~2010-05-04 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BE04C8A.7070907@redhat.com>
2010-05-04 16:45 ` I am trying to build an MLS livecd Stephen Smalley
2010-05-04 18:18 ` Daniel J Walsh [this message]
2010-05-04 18:39 ` Stephen Smalley
2010-05-04 18:46 ` Stephen Smalley
2010-05-04 18:56 ` Daniel J Walsh
2010-05-04 19:38 ` Stephen Smalley
2010-05-04 20:39 ` Eric Paris
2010-05-04 20:44 ` Stephen Smalley
2010-05-04 20:57 ` Eric Paris
2010-05-04 21:41 ` Daniel J Walsh
2010-05-05 20:17 ` Daniel J Walsh
2010-05-04 20:46 ` Eric Paris
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=4BE064F2.3060505@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@redhat.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.