linux-kernel - Re: [PATCH] ptrace: allow to ptrace /sbin/init

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47EB4AB4.7070704@openvz.org>
Date:	Thu, 27 Mar 2008 10:20:20 +0300
From:	Pavel Emelyanov <xemul@...nvz.org>
To:	Oleg Nesterov <oleg@...sign.ru>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Herbert Poetzl <herbert@...hfloor.at>,
	Krzysztof Halasa <khc@...waw.pl>, Pavel Machek <pavel@....cz>,
	"Serge E. Hallyn" <serue@...ibm.com>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Roland McGrath <roland@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ptrace: allow to ptrace /sbin/init

Oleg Nesterov wrote:
> Afaics, currently there are no kernel problems with ptracing init, it can't
> lose SIGNAL_UNKILLABLE flag and be killed/stopped by accident.
> 
> The ability to strace/debug init can be very useful if you try to figure
> out why it does not work as expected.
> 
> However, admin should know what he does, "gdb /sbin/init 1" stops init, it
> can't reap orphaned zombies or take care of /etc/inittab until continued.
> It is even possible to crash init (and thus the whole system) if you wish,
> ptracer has full control.
> 
> See also the long discussion: http://marc.info/?t=120628018600001
> 
> Signed-off-by: Oleg Nesterov <oleg@...sign.ru>

Acked-by: Pavel Emelyanov <xemul@...nvz.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/