From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Chris Grier <grier@uiuc.edu>
Cc: Colin Walters <walters@verbum.org>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: policy questions and bugs
Date: Thu, 20 May 2004 06:26:58 +0000 [thread overview]
Message-ID: <20040520062656.GI24597@lkcl.net> (raw)
In-Reply-To: <20040519200759.GA13982@balder>
On Wed, May 19, 2004 at 03:07:59PM -0500, Chris Grier wrote:
> > ----- Forwarded message from Colin Walters <walters@verbum.org> -----
> >
> > > When running some services, I would like them to run as a non root uid
> > > and gid (ircd and oidentd are the services which I usually do this
> > > with), which I normally do with su. When we do this with selinux
> > > running, we are prompted to enter a role and type (not select from a
> > > list). Is this just a matter of defining a transition to acommodate for
> > > this to happen?
> >
> > You run "su" interactively from a root shell? I'd suggest instead using
> > init scripts.
>
> No, not interactively. I am trying to use the init scripts. The way it
> works is the init function daemon() (from /etc/init.d/functions)
> accepts a --user argument to run the daemon as a given user.
oo. ah. yes, i have some scripts that need to be run under
specific user contexts, too.
i use /sbin/start-stop-daemon with a "-u lkcl" argument.
is /sbin/start-stop-daemon going to need to be updated, too,
to have a get_default_context() call in it?
l.
--
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:[~2004-05-20 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 3:30 policy questions and bugs Chris Grier
2004-05-15 17:06 ` Colin Walters
2004-05-19 20:07 ` Chris Grier
2004-05-19 21:04 ` Russell Coker
2004-05-20 6:26 ` Luke Kenneth Casson Leighton [this message]
2004-05-15 21:29 ` Russell Coker
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=20040520062656.GI24597@lkcl.net \
--to=lkcl@lkcl.net \
--cc=SELinux@tycho.nsa.gov \
--cc=grier@uiuc.edu \
--cc=walters@verbum.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.