From: Vikram Ambrose <Vikram.Ambrose@windriver.com>
To: russell@coker.com.au
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: PAM security transitions
Date: Mon, 25 Aug 2008 09:20:58 -0400 [thread overview]
Message-ID: <48B2B1BA.5040907@windriver.com> (raw)
In-Reply-To: <200808231150.37055.russell@coker.com.au>
Russell Coker wrote:
> On Saturday 23 August 2008 06:29, Vikram Ambrose
> <Vikram.Ambrose@windriver.com> wrote:
>
>> I've been messing around with various modules and installations and I've
>> come across a strange PAM problem. Without any SELinux support in
>> pam.d/login, root's shell gets system_r:local_login_t
>>
>
> Yes, ages ago it was decided not to maintain patches for the various terminal
> login programs and to instead use a PAM module.
>
>
>> But then using: pam_selinux.so close/open, root's shell gets
>> root:staff_r:system_chkpwd_t
>>
>
> I think that was a policy bug, it's fixed if you use all the latest versions.
>
> What version of the policy is running on the machines in question?
>
>
Strange, that box is running the latest. Refpolicy svn-2787 and Selinux
svn-2950
Could you tell me a little more about that bug, and how it came about?
Vikram
--
Vikram Ambrose | Linux Products Division | WindRiver Corporation
--
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:[~2008-08-25 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:29 PAM security transitions Vikram Ambrose
2008-08-23 1:50 ` Russell Coker
2008-08-25 13:20 ` Vikram Ambrose [this message]
2008-08-25 11:45 ` Stephen Smalley
2008-08-26 15:08 ` Daniel J Walsh
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=48B2B1BA.5040907@windriver.com \
--to=vikram.ambrose@windriver.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.