mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Oleg Nesterov <oleg@tv-sign.ru>, Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Emelyanov <xemul@openvz.org>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org,
	"Serge E. Hallyn" <serue@us.ibm.com>,
	Chris Wright <chrisw@sous-sol.org>,
	Andrew Morgan <morgan@kernel.org>
Subject: Re: [PATCH] ptrace: it is fun to strace /sbin/init
Date: Tue, 25 Mar 2008 08:40:01 -0500	[thread overview]
Message-ID: <20080325134001.GB5984@sergelap.austin.rr.com> (raw)
In-Reply-To: <1206446637.3302.134.camel@moss-spartans.epoch.ncsc.mil>

Quoting Stephen Smalley (sds@tycho.nsa.gov):
> 
> On Tue, 2008-03-25 at 02:04 +0300, Oleg Nesterov wrote:
> > On 03/24, Pavel Machek wrote:
> > >
> > > > /sbin/init is important, but there are other important (and sometimes
> > > > much more important) services. Why it is so special so that we can't
> > > > debug/strace it?
> > > 
> > > Maybe. Let's kill /sbin/init protection in 2.6.26. But making it
> > > optional is wrong.
> > 
> > You are right, the boot parameter is silly. How about sysctl?
> > 
> > Stephen, do you see any security problems if we make /sbin/init
> > ptraceable by default?
> 
> Not an issue for SELinux (we apply an orthogonal check based on security
> context, so we can already block ptrace of init independent of whether
> root/CAP_SYS_PTRACE can do it).  I'm not sure though as to whether
> people using capabilities have ever relied on this special protection of
> init (e.g. custom init spawns children with lesser capabilities and
> relies on the fact that they cannot ptrace init to effectively re-gain
> those capabilities, even if they possess CAP_SYS_PTRACE).

Still thinking it through, but it seems like special casing init isn't
useful.  There are likely to be other tasks with all capabilities
set which the malicious task could just as well ptrace to do his
mischief, right?

thanks,
-serge

  reply	other threads:[~2008-03-25 13:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 13:51 Oleg Nesterov
2008-03-24 16:01 ` Pavel Machek
2008-03-24 16:40   ` Oleg Nesterov
2008-03-24 22:39     ` Pavel Machek
2008-03-24 23:04       ` Oleg Nesterov
2008-03-24 23:09         ` Pavel Machek
2008-03-24 23:18           ` Oleg Nesterov
2008-03-24 23:26             ` Andrew Morton
2008-03-24 23:38               ` Oleg Nesterov
2008-03-25 12:03         ` Stephen Smalley
2008-03-25 13:40           ` Serge E. Hallyn [this message]
2008-03-25 14:37             ` Stephen Smalley
2008-03-25 18:06               ` Serge E. Hallyn
2008-03-25 19:07                 ` Herbert Poetzl
2008-03-25 21:55                 ` Pavel Machek
2008-03-26 15:31                   ` Andrew Morgan
2008-03-26 15:47                 ` Pavel Emelyanov
2008-03-24 22:29 ` Andrew Morton
2008-03-24 22:56   ` Oleg Nesterov
2008-03-24 23:08     ` Andrew Morton
2008-03-24 23:29       ` Oleg Nesterov
2008-03-25 10:00       ` Andi Kleen
2008-03-25 14:16         ` Krzysztof Halasa
2008-03-25 14:22           ` Andi Kleen
2008-03-25 14:30             ` Krzysztof Halasa
2008-03-25 14:35               ` Andi Kleen
2008-03-25 14:58                 ` Krzysztof Halasa
2008-03-25 14:47             ` Pavel Machek
2008-03-25 14:56               ` Andi Kleen
2008-03-25 17:42         ` Oleg Nesterov
2008-03-25 22:00         ` Roland McGrath

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=20080325134001.GB5984@sergelap.austin.rr.com \
    --to=serue@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=pavel@ucw.cz \
    --cc=roland@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=xemul@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®