All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: selinux@tycho.nsa.gov
Subject: Re: [PATCH] genhomedircon: remove hardcoded refpolicy strings
Date: Wed, 7 Sep 2016 08:36:09 -0400	[thread overview]
Message-ID: <6550b4ea-b1bf-3b55-0829-a3f683c9170c@tycho.nsa.gov> (raw)
In-Reply-To: <20160907044233.GA3000@home>

On 09/07/2016 12:42 AM, Gary Tierney wrote:
> On Tue, Sep 06, 2016 at 03:13:17PM -0400, Stephen Smalley wrote:
>> On 09/06/2016 09:48 AM, Gary Tierney wrote:
>>> static int seuser_sort_func(const void *arg1, const void
>>> *arg2) @@ -1074,9 +1130,6 @@ static genhomedircon_user_entry_t 
>>> *get_users(genhomedircon_settings_t * s, if (strcmp(name,
>>> DEFAULT_LOGIN) == 0) continue;
>>> 
>>> -        if (strcmp(name, TEMPLATE_SEUSER) == 0) -
>>> continue; -
>> 
>> This yields a warning/error on Fedora: $ sudo semodule -B 
>> libsemanage.add_user: user system_u not in password file
>> 
> 
> I can re-add this conditional to prevent outputting the warning,
> though is there a reason for a login named "system_u" ?

crond used to require one in order to look up the context for system
cron jobs; I'm not sure if that is still required, but it is still
present in Fedora.

  parent reply	other threads:[~2016-09-07 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 13:48 [PATCH] remove system_u and s0 hardcoded strings Gary Tierney
2016-09-06 13:48 ` [PATCH] genhomedircon: remove hardcoded refpolicy strings Gary Tierney
2016-09-06 19:13   ` Stephen Smalley
2016-09-07  4:42     ` Gary Tierney
2016-09-07  7:15       ` Dominick Grift
2016-09-07 12:45         ` Stephen Smalley
2016-09-07 12:45           ` Dominick Grift
2016-09-07 12:36       ` Stephen Smalley [this message]
2016-09-07 12:47         ` Dominick Grift
2016-09-07 12:55           ` Dominick Grift
2016-09-07 13:00           ` Stephen Smalley
2016-09-07 13:04             ` Dominick Grift
2016-09-07 13:08               ` 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=6550b4ea-b1bf-3b55-0829-a3f683c9170c@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --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.