All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Russell Coker <rcoker@redhat.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: start of patch to dpkg's start-stop-daemon
Date: Thu, 20 May 2004 17:48:03 +0000	[thread overview]
Message-ID: <20040520174803.GA18182@lkcl.net> (raw)
In-Reply-To: <200405210333.37234.rcoker@redhat.com>

On Fri, May 21, 2004 at 03:33:37AM +1000, Russell Coker wrote:
> On Fri, 21 May 2004 02:23, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> > > > it's a patch to dpkg 1.10.21's utils/start-stop-daemon.c
> > > > which causes a context switch just before
> > > > the setuid/setgid calls.
> > >
> > > What is the benefit in that?
> >
> >  it's easier than breaking pre-existing /etc/init.d/* scripts where
> >  people expect the -u option to act as it should?
> 
> How is it broken?  initrc_t has setuid and setgid capabilities so SE Linux 
> does not stop the regular function of start-stop-daemon.
 
 ..o*??  ah, cool, that's very smart, i wasn't expecting that.

 i learn something new every day :)

> >  in other words, the benefit in patching start-stop-daemon is to
> >  provide legacy transition support.
> 
> My systems have been working fine with a non-patched start-stop-daemon for two 
> years.  When I first started working on SE Linux I had a similar idea to 
> avoid the use of run_init, that turned out to be a bad idea and I've been 
> using the regular start-stop-daemon since then.
> 
> >  i _really_ don't want the -u option on my custom /etc/init.d/custom
> >  script to suddenly start running the daemon as root.
> 
> Why not?
 
 ignore all the rest of my comments: they were based on the assumption
 that initrc_t would not allow setuid or setgid.

 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.

      reply	other threads:[~2004-05-20 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20  8:43 start of patch to dpkg's start-stop-daemon Luke Kenneth Casson Leighton
2004-05-20 15:32 ` Russell Coker
2004-05-20 16:23   ` Luke Kenneth Casson Leighton
2004-05-20 17:33     ` Russell Coker
2004-05-20 17:48       ` Luke Kenneth Casson Leighton [this message]

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=20040520174803.GA18182@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=rcoker@redhat.com \
    --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.