All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: Russell Coker <russell@coker.com.au>
Cc: nagray@bruzenak.com, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: What causes this??
Date: Tue, 2 Dec 2003 12:43:39 +0000	[thread overview]
Message-ID: <20031202124339.GT11972@vnl.com> (raw)
In-Reply-To: <200312021549.34383.russell@coker.com.au>

> On Tue, 2 Dec 2003 15:45, Nick <nagray@bruzenak.com> wrote:
> I just rebuilt a system and when I try to change roles I get this
>
>
> [root@hawaii SELinux]# newrole -r sysadm_r
> cannot find your entry in the passwd file.
> [root@hawaii SELinux]#

If this is a new install, then either you have to
add a line to pam.d/login for pam_selinux.so or
else you have to get Colin Walters login package.

The pam.d solution seems to be the preferred one
by other debian users here (although I'm currently
using the other way).

It's a problem because debian standards don't
seem to allow any way to handle this step other
than by manual incantations.

-- 
------------------------------------------------------
   Dale Amon     amon@islandone.org    +44-7802-188325
       International linux systems consultancy
     Hardware & software system design, security
    and networking, systems programming and Admin
	      "Have Laptop, Will Travel"
------------------------------------------------------

--
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.

  reply	other threads:[~2003-12-02 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1070340338.12612.2.camel@hawaii>
2003-12-02  4:49 ` What causes this?? Russell Coker
2003-12-02 12:43   ` Dale Amon [this message]
2003-12-02 14:47   ` Nick
2003-12-02 15:13     ` Russell Coker
2003-12-02 16:28     ` Stephen Smalley
2003-12-03 11:02       ` Dale Amon
2003-12-02  5:39 Nick

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=20031202124339.GT11972@vnl.com \
    --to=amon@vnl.com \
    --cc=nagray@bruzenak.com \
    --cc=russell@coker.com.au \
    --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.