All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diyab <diyab@diyab.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: lky <lky77@sjtu.edu.cn>, SELINUX <SELinux@tycho.nsa.gov>
Subject: Re: question about su and passwd
Date: Mon, 27 Oct 2003 19:53:14 -0500	[thread overview]
Message-ID: <3F9DBDFA.908@diyab.net> (raw)
In-Reply-To: <1067268199.18818.59.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:

> On Sat, 2003-10-25 at 18:48, Diyab wrote:
> 
>>passwd, like most of the other user management tools, requires a
>>selinux specific version called spasswd.  There are some file labeling
>>issues which the normal passwd program can not handle and that is why
>>the modified version was made.  If you search the list archives you can
>>find out more information about that.
> 
> 
> The spasswd wrappers were replaced with direct patches to the base
> programs by Dan Walsh when the code was ported to the new SELinux API.
> This allows the files to be directly created in the right context and
> eliminates the window where the passwd file is in a more restrictive
> context than necessary.
> 

Ah, my apoligies.  I have not had the opportunity to upgrade to the 
newer releases yet and I was not aware of the change.  Thanks for 
pointing this out Stephen.

Timothy,

-- 
I put instant coffee in a microwave and almost went back in time.
		-- Steven Wright


--
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-10-28  0:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 21:20 question about su and passwd lky
2003-10-25 22:48 ` Diyab
2003-10-25  6:23   ` lky
2003-10-27 15:23   ` Stephen Smalley
2003-10-28  0:53     ` Diyab [this message]
2003-10-27 14:52 ` Stephen Smalley
2003-10-27 15:01   ` Russell Coker
2003-10-27 16:42     ` lky
2003-10-27 18:26   ` lky
2003-10-27 18:32     ` 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=3F9DBDFA.908@diyab.net \
    --to=diyab@diyab.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=lky77@sjtu.edu.cn \
    --cc=sds@epoch.ncsc.mil \
    /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.