| 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
| ||
|
Message-Id: <200612271935.07835.vda.linux@googlemail.com> Date: Wed, 27 Dec 2006 19:35:07 +0100 From: Denis Vlasenko <vda.linux@...glemail.com> To: ray-gmail@...rabbit.org Cc: "Rob Landley" <rob@...dley.net>, linux-kernel@...r.kernel.org, "David McCullough" <david_mccullough@...securecomputing.com> Subject: Re: Feature request: exec self for NOMMU. On Wednesday 27 December 2006 06:13, Ray Lee wrote: > On 12/26/06, Rob Landley <rob@...dley.net> wrote: > > I'm trying to make some nommu-friendly busybox-like tools, which means using > > vfork() instead of fork(). This means that after I fork I have to exec in > > the child to unblock the parent, and if I want to exec my current executable > > I have to find out where it lives so I can feed the path to exec(). This is > > nontrivial. > > > > Worse, it's not always possible. If chroot() has happened since the program > > started, there may not _be_ a path to my current executable available from > > this process's current or root directories. > > How about openning an fd to yourself at the beginning of execution, then calling > fexecve later? This solves chroot problem. How to find path-to-yourself reliably (for one, without using /proc/self/exe) is not obvious to me. -- vda - 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/
Powered by blists - more mailing lists