selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org
Cc: Petr Lautrbach <plautrba@redhat.com>
Subject: [RFC PATCH 0/2] userspace: Allow changing version of kernel policy built by semodule
Date: Thu,  6 Feb 2020 14:12:51 +0100	[thread overview]
Message-ID: <20200206131253.535302-1-omosnace@redhat.com> (raw)

See the second patch for motivation.

Passed Travis: https://travis-ci.org/WOnder93/selinux/builds/646845127

Ondrej Mosnacek (2):
  libsemanage: support changing policy version via API
  semodule: support changing policyvers via command line

 libsemanage/include/semanage/handle.h |  6 +++
 libsemanage/src/direct_api.c          |  9 ++++-
 libsemanage/src/handle.c              | 24 ++++++++++++
 libsemanage/src/handle.h              |  1 +
 libsemanage/src/libsemanage.map       |  6 +++
 libsemanage/src/semanage_store.c      | 54 ++++++++++++++++-----------
 libsemanage/src/semanage_store.h      |  6 ++-
 policycoreutils/semodule/semodule.8   |  3 ++
 policycoreutils/semodule/semodule.c   | 12 +++++-
 9 files changed, 95 insertions(+), 26 deletions(-)

-- 
2.24.1


             reply	other threads:[~2020-02-06 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 13:12 Ondrej Mosnacek [this message]
2020-02-06 13:12 ` [RFC PATCH 1/2] libsemanage: support changing policy version via API Ondrej Mosnacek
2020-02-06 13:12 ` [RFC PATCH 2/2] semodule: support changing policyvers via command line Ondrej Mosnacek
2020-02-06 13:45   ` Stephen Smalley
2020-02-06 14:19     ` Ondrej Mosnacek
2020-02-06 14:52       ` Stephen Smalley
2020-02-06 15:28         ` Ondrej Mosnacek
2020-02-06 15:35           ` Stephen Smalley
2020-02-06 18:47             ` Stephen Smalley
2020-02-06 19:22               ` Stephen Smalley

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=20200206131253.535302-1-omosnace@redhat.com \
    --to=omosnace@redhat.com \
    --cc=plautrba@redhat.com \
    --cc=selinux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).