From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: Semodule syntax is broken.
Date: Fri, 21 Aug 2009 11:53:29 -0400 [thread overview]
Message-ID: <4A8EC2F9.3040707@redhat.com> (raw)
Currently when rpm ships, it does an
semodule -b base.pp -i a.pp b,pp c.pp
It should be able to do
semodule -b base.pp -u a.pp b.pp c.pp
But -u blows up if c.pp was not previously installed. It should follow the rpm -U syntax; upgrade if the previous package exists and install if it does not. If we want to add a -F (freshen) this could only upgrade pre-existing modules, and ignore others.
If I was to change to -u, I would need to add a fourth field to policy modules and upgrade it each time I added a patch. It would be a pain, but I guess I could deal with it.
BUT A bigger problem is how to deal with an administrator that wants to remove a package and ensure it does not get reinstalled. If an administrator decides he does not want to install unconfined.pp, we do not want an selinux-policy upgrade to re-install the package.
semodule -r should set a flag when a package gets removed. Then semodule -u or semodule -i would not install the package unless the administrator specifies a -f.
semodule -r unconfined
Would create a file in the policy store /etc/selinux/targeted/modules/active/modules/unconfined.exclude.
semodule -u and semodule -i would respect, and just print out an error message.
semodule -u unconfined.pp
Warning: unconfined.pp is excluded from the policy store, use -f to force the install
Add -q qualifier to quiet this message
# semodule -f -u unconfined.pp
Would install the package and remove the flag.
I would like to get consensus on this before I implement. Or others can implement.
--
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 reply other threads:[~2009-08-21 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 15:53 Daniel J Walsh [this message]
2009-08-21 16:27 ` Semodule syntax is broken Manoj Srivastava
2009-08-21 17:50 ` Daniel J Walsh
2009-08-22 3:27 ` Manoj Srivastava
2009-08-24 13:04 ` Daniel J Walsh
2009-08-24 20:19 ` Chad Sellers
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=4A8EC2F9.3040707@redhat.com \
--to=dwalsh@redhat.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.