From: Dale Amon <amon@vnl.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: nagray@austin.rr.com, Russell Coker <russell@coker.com.au>,
nagray@bruzenak.com, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: What causes this??
Date: Wed, 3 Dec 2003 11:02:26 +0000 [thread overview]
Message-ID: <20031203110225.GA25416@vnl.com> (raw)
In-Reply-To: <1070382538.14253.65.camel@moss-spartans.epoch.ncsc.mil>
On Tue, Dec 02, 2003 at 11:28:58AM -0500, Stephen Smalley wrote:
> On Tue, 2003-12-02 at 09:47, Nick wrote:
> > id -c
> > system_u:system_r:sysadm_t
>
> This implies that you aren't running the patched login program (or,
> alternatively, using the pam_selinux module). Note that the user
> identity portion of the context wasn't set, which is why newrole is
> confused.
Stephen, just a modest and time saving suggestion. Why
not add a bit of code to detect this particular condition
and print a message stating the probable solution?
--
------------------------------------------------------
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.
next prev parent reply other threads:[~2003-12-03 11:02 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
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 [this message]
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=20031203110225.GA25416@vnl.com \
--to=amon@vnl.com \
--cc=nagray@austin.rr.com \
--cc=nagray@bruzenak.com \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--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.