From: Daniel J Walsh <dwalsh@redhat.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: tresys <refpolicy@oss1.tresys.com>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy] what to do: libsemanage.get_home_dirs:
Date: Tue, 09 Mar 2010 16:03:06 -0500 [thread overview]
Message-ID: <4B96B78A.4020801@redhat.com> (raw)
In-Reply-To: <dd18b0c31003091001n5b5ab089g3829823e256ae86e@mail.gmail.com>
On 03/09/2010 01:01 PM, Justin Mattock wrote:
> with the latest policy on open suse 11.2
> I'm seeing this after building the policy:
> libsemanage.get_home_dirs: nobody homedir /var/lib/nobody or its
> parent directory conflicts with a file context already specified in
> the policy. This usually indicates an incorrectly defined system
> account. If it is a system account please make sure its uid is less
> than 1000 or its login shell is /sbin/nologin.
>
> with using an older policy on this system, I never saw this.
>
> what to do?
>
>
/var/lib/nobody record in /etc/passwd needs to have a shell of
/bin/false or /sbin/nologin or a UID < 500.
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] what to do: libsemanage.get_home_dirs:
Date: Tue, 09 Mar 2010 16:03:06 -0500 [thread overview]
Message-ID: <4B96B78A.4020801@redhat.com> (raw)
In-Reply-To: <dd18b0c31003091001n5b5ab089g3829823e256ae86e@mail.gmail.com>
On 03/09/2010 01:01 PM, Justin Mattock wrote:
> with the latest policy on open suse 11.2
> I'm seeing this after building the policy:
> libsemanage.get_home_dirs: nobody homedir /var/lib/nobody or its
> parent directory conflicts with a file context already specified in
> the policy. This usually indicates an incorrectly defined system
> account. If it is a system account please make sure its uid is less
> than 1000 or its login shell is /sbin/nologin.
>
> with using an older policy on this system, I never saw this.
>
> what to do?
>
>
/var/lib/nobody record in /etc/passwd needs to have a shell of
/bin/false or /sbin/nologin or a UID < 500.
next prev parent reply other threads:[~2010-03-09 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 18:01 what to do: libsemanage.get_home_dirs: Justin Mattock
2010-03-09 18:01 ` [refpolicy] " Justin Mattock
2010-03-09 21:03 ` Daniel J Walsh [this message]
2010-03-09 21:03 ` Daniel J Walsh
2010-03-09 22:29 ` Justin P. Mattock
2010-03-09 22:29 ` Justin P. Mattock
2010-03-10 15:35 ` Alan Rouse
2010-03-10 15:35 ` Alan Rouse
2010-03-10 15:45 ` Justin P. Mattock
2010-03-10 15:45 ` Justin P. Mattock
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=4B96B78A.4020801@redhat.com \
--to=dwalsh@redhat.com \
--cc=justinmattock@gmail.com \
--cc=refpolicy@oss1.tresys.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.