linux-kernel - Re: [EXAMPLE CODE] Parasite thread injection using PTRACE

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110720142129.GB19603@peqn>
Date:	Wed, 20 Jul 2011 09:21:29 -0500
From:	Serge Hallyn <serge.hallyn@...onical.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Pavel Emelyanov <xemul@...allels.com>,
	Nathan Lynch <ntl@...ox.com>,
	Oren Laadan <orenl@...columbia.edu>,
	Daniel Lezcano <dlezcano@...ibm.com>,
	Serge Hallyn <serge@...lyn.com>,
	Cyrill Gorcunov <gorcunov@...il.com>,
	Glauber Costa <glommer@...allels.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Containers <containers@...ts.osdl.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [EXAMPLE CODE] Parasite thread injection using PTRACE_SEIZE and
 friends

Quoting Tejun Heo (tj@...nel.org):
> On Wed, Jul 20, 2011 at 04:00:37PM +0200, Tejun Heo wrote:
> > With new ptrace requests, a process can be captured and manipulated
> > practically transparently.  Other than syscall retry or -EINTR failure
> > in special cases and timing difference, everything including job
> > control stop state stays transparent across ptrace operations.
> 
> Ooh, forgot to mention something.  The ptracer can also reliably
> determine whether job control stop is in effect or not, so the whole
> job control state can be captured.

It sounds cool, thanks.  Is this completely separate from Pavel's
CR patchset (which I've not yet gotten around to looking at in
detail)?

-serge
--
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/