linux-kernel - Re: Feature request: exec self for NOMMU.

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: <4592C038.8010407@madrabbit.org>
Date:	Wed, 27 Dec 2006 10:49:28 -0800
From:	Ray Lee <ray-lk@...rabbit.org>
To:	Rob Landley <rob@...dley.net>
Cc:	Vadim Lobanov <vlobanov@...akeasy.net>, ray-gmail@...rabbit.org,
	linux-kernel@...r.kernel.org,
	David McCullough <david_mccullough@...securecomputing.com>
Subject: Re: Feature request: exec self for NOMMU.

Rob Landley wrote:
> On Wednesday 27 December 2006 1:08 am, Vadim Lobanov wrote:
>> On Wed, 2006-12-27 at 00:51 -0500, Rob Landley wrote:
>>> On Wednesday 27 December 2006 12:13 am, Ray Lee wrote:
>>>> How about openning an fd to yourself at the beginning of execution, then
>>>> calling fexecve later?
>>> I haven't got a man page for fexecve.  Does libc have it?
>> It's implemented inside glibc, and uses /proc to execve() the file that
>> the fd points to.

Oh, hmm. Then I think it won't work, will it? I'd assumed fexecve was
implemented in kernel.

> Cute, and I can do that.  Assuming /proc is mounted in the chroot 
> environment...

Maybe I'm just confused -- wouldn't be the first time -- but if it's
implemented inside userspace, then once you chroot() you won't be able
to execute the path you find via /proc, will you?
-
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/