From: Dominick Grift <domg472@gmail.com>
To: Dennis Wronka <linuxweb@gmx.net>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Question about su
Date: Wed, 11 Feb 2009 11:46:36 +0100 [thread overview]
Message-ID: <1234349196.13112.16.camel@notebook1.grift.internal> (raw)
In-Reply-To: <200902111650.39754.linuxweb@gmx.net>
On Wed, 2009-02-11 at 16:50 +0800, Dennis Wronka wrote:
> What use is su if a normal user after running su is still user_u:user_r:user_t
> and thus has no permissions to do stuff?
user_t is an unprivileged user domain.
> Sure, he's root, but as because of SELinux that alone isn't worth much, as
> being user_u still limits the user's options pretty much.
user_t should not use root. user_t is confined to this domain. It is not
designed to "user" domain transition.
> Is there anything I misunderstand here? I don't think there should be an
> automtic transition from user_r to sysadm_r, and newrole-ing this doesn't work
> as user_u doesn't have the sysadmin-role.
staff_t is the domain that can use root by first running newrole -r
sysadm_r and then su.
> So, what the heck is the use of su on a SELinux-system?
It works but just not for user_t. Map users that should be able to
"user" domain transition to privileged roles to the staff_u SELinux user
group.
hth ,Dominick
> Thanks and best regards,
> Dennis
--
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:[~2009-02-11 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 8:50 Question about su Dennis Wronka
2009-02-11 10:46 ` Dominick Grift [this message]
2009-02-11 13:01 ` Dennis Wronka
2009-02-11 13:16 ` Dominick Grift
2009-02-11 15:59 ` Casey Schaufler
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=1234349196.13112.16.camel@notebook1.grift.internal \
--to=domg472@gmail.com \
--cc=linuxweb@gmx.net \
--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.