From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Brian Iván Martínez" <xangelux@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: systemd selinux
Date: Tue, 19 Feb 2013 08:37:05 -0500 [thread overview]
Message-ID: <51238001.5030804@tycho.nsa.gov> (raw)
In-Reply-To: <CACcxAnFy6v79Eiz5uA_Ac92c+kuJRhCi3BEw_ZkzG25G4etuSg@mail.gmail.com>
On 02/17/2013 01:43 AM, Brian Iván Martínez wrote:
> Thanks for the help, I found the fedora package for policycoreutils and
> copied the unit file to make the daemon run in every boot, you said it
> wasn't necessary but it would be nice to have working everything I can
> and even if I have the time and energy after this getting the gui tools
> too. Anyway, I've downloaded the selinux notebook and the first thing I
> notice is the change in the directories so I'm running thinking selinux
> was in /selinux and no it isn't, should I erase the entry in the fstab
> or should I change it to point to /sys/fs/selinux?. Another thing is, I
> installed an old policy wich is sysvinit compatible but now I can't boot
> in enforcing because it complains about not finding /dev/shm to boot (in
> permissive is fine), in the IRC one guy helped me (I'm really sorry, I
> forgot the username) and said it could be a policy issue so I should
> install a new one either from Fedora's lates packages or from Tresys and
> then try to create one based on those. My question is, could that be the
> issue or should I search somewhere else?
You don't need it in fstab because systemd calls libselinux
selinux_init_load_policy() which will automatically try to mount
selinuxfs on /sys/fs/selinux first, and then fall back to /selinux if
that directory does not exist (which would be the case on older kernels).
Updating to a recent policy certainly wouldn't hurt. But for policy
issues, you should:
a) post your actual denials,
b) take your questions to the refpolicy list,
http://oss.tresys.com/mailman/listinfo/refpolicy
--
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:[~2013-02-19 13:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 19:21 Brian Iván Martínez
2013-02-11 19:00 ` pam_selinux Stephen Smalley
2013-02-11 19:17 ` pam_selinux Brian Iván Martínez
2013-02-11 19:29 ` systemd selinux Stephen Smalley
2013-02-11 19:31 ` Brian Iván Martínez
2013-02-11 20:17 ` Stephen Smalley
2013-02-11 20:21 ` Brian Iván Martínez
2013-02-11 20:22 ` Brian Iván Martínez
2013-02-11 20:41 ` Stephen Smalley
2013-02-11 20:54 ` Brian Iván Martínez
2013-02-11 21:00 ` Stephen Smalley
2013-02-11 21:02 ` Brian Iván Martínez
2013-02-11 23:01 ` Brian Iván Martínez
2013-02-12 12:54 ` Stephen Smalley
2013-02-13 0:53 ` Brian Iván Martínez
2013-02-13 13:32 ` Stephen Smalley
2013-02-17 6:43 ` Brian Iván Martínez
2013-02-19 13:37 ` Stephen Smalley [this message]
2013-02-19 15:20 ` Brian Iván Martínez
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=51238001.5030804@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=xangelux@gmail.com \
/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.