From: Diyab <diyab@diyab.net>
To: lky <lky77@sjtu.edu.cn>
Cc: SELINUX <SELinux@tycho.nsa.gov>
Subject: Re: question about su and passwd
Date: Sat, 25 Oct 2003 18:48:16 -0400 [thread overview]
Message-ID: <3F9AFDB0.1020406@diyab.net> (raw)
In-Reply-To: <001401c39a74$ac06b370$5d38a8c0@lky>
lky wrote:
> Hi, When I change the account with su I found the security context
> didn't change( the 2 account have different contexts ). Should I use
> aother command?
> Another problem is I couldn't change my passwd under enforced mode.When
> I login as root and run "passwd" it said I coundn't do that while when I
> login as another general user and run "passwd" it let me input my Unix
> passwd but always fail. Who can tell me the reason? I have installed
> 2.6-based SELinux and the patched utilities on redhat9.0.
> Thanks!
Su will only change your user id not your context. To change your
context you have to use newrole and it's best to do that before running
su. 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.
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.
next prev parent reply other threads:[~2003-10-25 22:48 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 [this message]
2003-10-25 6:23 ` lky
2003-10-27 15:23 ` Stephen Smalley
2003-10-28 0:53 ` Diyab
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=3F9AFDB0.1020406@diyab.net \
--to=diyab@diyab.net \
--cc=SELinux@tycho.nsa.gov \
--cc=lky77@sjtu.edu.cn \
/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.