All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: selinux@vger.kernel.org
Cc: Dominick Grift <dac.override@gmail.com>
Subject: [RFC 2/3] semanage: do not default prefix to "user"
Date: Sat, 23 Nov 2019 15:42:44 +0100	[thread overview]
Message-ID: <20191123144245.3079306-3-dac.override@gmail.com> (raw)
In-Reply-To: <20191123144245.3079306-1-dac.override@gmail.com>

By default `semanage-user -m ...` resets the prefix to "user". We need it not to. Defaulting to '' results is no change to the current prefix.

Signed-off-by: Dominick Grift <dac.override@gmail.com>
---
 python/semanage/semanage | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/semanage/semanage b/python/semanage/semanage
index b2fabea6..e5abfdd2 100644
--- a/python/semanage/semanage
+++ b/python/semanage/semanage
@@ -425,7 +425,7 @@ def setupUserParser(subparsers):
                             help=_('''
 SELinux Roles.  You must enclose multiple roles within quotes, separate by spaces. Or specify -R multiple times.
 '''))
-    userParser.add_argument('-P', '--prefix', default="user", help=argparse.SUPPRESS)
+    userParser.add_argument('-P', '--prefix', default='', help=argparse.SUPPRESS)
     userParser.add_argument('selinux_name', nargs='?', default=None, help=_('selinux_name'))
     userParser.set_defaults(func=handleUser)
 
-- 
2.24.0


  parent reply	other threads:[~2019-11-23 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 14:42 [RFC 0/3] Second phase of UserPrefix to UserRBACSEPRole transition Dominick Grift
2019-11-23 14:42 ` [RFC 1/3] libsemanage: fall back to valid "object_r" role instead of "user" prefix string Dominick Grift
2019-11-23 14:42 ` Dominick Grift [this message]
2019-11-23 14:42 ` [RFC 3/3] cil: qualify roles from symtable when resolving userprefix Dominick Grift
2019-11-25 13:24 ` [RFC 0/3] Second phase of UserPrefix to UserRBACSEPRole transition Stephen Smalley
2019-11-25 13:50   ` Dominick Grift
2019-11-25 14:10   ` Dominick Grift
2019-11-26 18:27     ` Stephen Smalley
2019-11-27 11:22       ` Dominick Grift
2019-11-27 15:03         ` Stephen Smalley
2019-11-27 15:25           ` Dominick Grift

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=20191123144245.3079306-3-dac.override@gmail.com \
    --to=dac.override@gmail.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 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.