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 14:16:59 +0100 [thread overview]
Message-ID: <1234358219.14058.3.camel@notebook1.grift.internal> (raw)
In-Reply-To: <200902112101.05913.linuxweb@gmx.net>
On Wed, 2009-02-11 at 21:01 +0800, Dennis Wronka wrote:
> Thanks. This info helped a lot.
> So user_u is for regular users that are just supposed to do stuff with what
> the system offers. Anything else, like installing stuff is loaded off to users
> that are at least staff_u or above.
>
> It's something one has to get used to, especially the part of newrole-ing
> first and afterwards using su.
In Fedora (targeted policy) we use sudo to transition to root and
privileged user domains. This has the advantage that one can delegate
privileged tasks without having to share roots password. It also saves
you from having to authenticate two times.
Yes user_u is for users that should never be able to do privileged
tasks.
Staff_u can domain transition to more permissive user domains.
> > --
> > 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.
>
--
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 13:17 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
2009-02-11 13:01 ` Dennis Wronka
2009-02-11 13:16 ` Dominick Grift [this message]
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=1234358219.14058.3.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.