From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
sequel@neofreak.org, SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: root and change of passwords
Date: Tue, 11 Jan 2005 11:06:38 -0500 [thread overview]
Message-ID: <41E3F98E.2030400@redhat.com> (raw)
In-Reply-To: <1105456202.7682.18.camel@selinux>
Christopher J. PeBenito wrote:
>On Tue, 2005-01-11 at 08:59 -0500, Stephen Smalley wrote:
>
>
>>On Fri, 2005-01-07 at 14:09, DeadManMoving wrote:
>>
>>
>>>i've recently find a bug in the implementation of SELinux in gentoo
>>>Still willing to fix that, i've given the red hat passwd suite a try on
>>>my gentoo installation and yes! it works quite well!
>>>
>>>
>>IIRC, the Fedora passwd program obtains the caller's security context,
>>extracts the user identity from it, and checks a SELinux permission if
>>attempting to change the passwd information for a user other than the
>>caller. Note that the user identity in the security context can only
>>be set by processes allowed to do so by SELinux policy and is not
>>necessarily the same as the Linux uid, so a rogue uid 0 process cannot
>>arbitrarily assume the SELinux user identity of "root".
>>
>>
>
>I was writing up a patch for shadow's version of passwd, chfn, and chsh,
>when I noticed that chage doesn't have a check. Is chage not included
>in Fedora, or was it determined that it didn't need a check?
>
>
>
chage comes from shadow-utils in Fedora/RHEL
--
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:[~2005-01-11 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 19:09 root and change of passwords DeadManMoving
2005-01-11 13:59 ` Stephen Smalley
2005-01-11 15:10 ` Christopher J. PeBenito
2005-01-11 15:59 ` Stephen Smalley
2005-01-11 16:06 ` Daniel J Walsh [this message]
2005-01-12 22:14 ` 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=41E3F98E.2030400@redhat.com \
--to=dwalsh@redhat.com \
--cc=cpebenito@tresys.com \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
--cc=sequel@neofreak.org \
/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.