From: Pavel Machek <pavel@ucw.cz>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Emelyanov <xemul@openvz.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptrace: it is fun to strace /sbin/init
Date: Mon, 24 Mar 2008 23:39:25 +0100 [thread overview]
Message-ID: <20080324223925.GD2426@elf.ucw.cz> (raw)
In-Reply-To: <20080324164059.GA4767@tv-sign.ru>
> > > @@ -803,6 +803,8 @@ and is between 256 and 4096 characters.
> > > Run specified binary instead of /sbin/init as init
> > > process.
> > >
> > > + init_ptrace [KNL] Allows to ptrace init.
> > > +
> >
> > No words about it being dangerous, but I believe it is.
>
> it is, admin should know what he does,
>
> > If it is not, lets do the patch, but not optional.
>
> This will change the default historical behaviour, I can't predict
> does this matter for (say) SELinux or not. Otherwise I'd personally
> prefer to always allow to ptrace init.
>
> > If it is dangerous, option does not make it better.
>
> ptrace() is always dangerous. ptracer can crash oracle and lose data.
>
> /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.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
pomozte zachranit klanovicky les: http://www.ujezdskystrom.info/
next prev parent reply other threads:[~2008-03-24 22:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 13:51 [PATCH] ptrace: it is fun to strace /sbin/init Oleg Nesterov
2008-03-24 16:01 ` Pavel Machek
2008-03-24 16:40 ` Oleg Nesterov
2008-03-24 22:39 ` Pavel Machek [this message]
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
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=20080324223925.GD2426@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--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