From: Thomas Downing <tdowning@bomgar.com>
To: <selinux@tycho.nsa.gov>
Subject: Newbie question on fixfiles
Date: Fri, 29 Jan 2016 11:25:21 -0600 [thread overview]
Message-ID: <1464190.SZXTM0cE5o@juss> (raw)
Hi,
I need to get SELinux running on an appliance we are building, not based on a
distro that already supports SELinux.
I've got all the userspace stuff built, (including setools3) without any
warnings or errors. I followed instructions for installing and loading
refpolicy, no warnings or errors. (Except the python tools, which all import
selinux.py, which does not seem to be included in the source tree.)
I'm booting with kernel options "security=selinux selinux=1", and dmesg shows
SELinux initializing, and no errors or warnings.
sestatus output:
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: refpolicy
Current mode: permissive
Mode from config file: permissive
Policy MLS status: disabled
Policy deny_unknown status: denied
Max kernel policy version: 30
Problem is: fixfiles does not actually label anything, and the underlying reason
is that none of the mounted disk filesystems (all ext4) have option 'seclabel'.
Any pointers?
Also, given the absence of the seclabel option, I question if the kernel part
of SELinux is in fact really happy...and if it isn't, I'm dead in the water
anyway.
Thanks much,
Thomas Downing
next reply other threads:[~2016-01-29 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 17:25 Thomas Downing [this message]
2016-01-29 17:37 ` Newbie question on fixfiles Joe Wulf
2016-01-29 18:26 ` Thomas Downing
2016-01-29 18:02 ` Stephen Smalley
2016-01-29 18:47 ` Stephen Smalley
2016-01-29 19:10 ` Thomas Downing
2016-01-29 19:03 ` Thomas Downing
2016-01-29 19:25 ` Stephen Smalley
2016-01-29 19:41 ` Thomas Downing
2016-01-29 20:05 ` Stephen Smalley
2016-01-29 20:13 ` Thomas Downing
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=1464190.SZXTM0cE5o@juss \
--to=tdowning@bomgar.com \
--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.