mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] allow execve'ing "/proc/self/exe" even if /proc is not  mounted
Date: Sat, 27 Jun 2009 00:55:32 +0200	[thread overview]
Message-ID: <1158166a0906261555k3f00e9bdi74960e9eb72a4bb7@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0906260626y36190ca9ia769c623d4c545d3@mail.gmail.com>

On Fri, Jun 26, 2009 at 3:26 PM, Mike Frysinger<vapier.adi@gmail.com> wrote:
> On Fri, Jun 26, 2009 at 04:00, Denys Vlasenko wrote:
>> On Thu, Jun 25, 2009 at 10:10 AM, Alan Cox wrote:
>>>> With this patch, it is possible to execute /proc/self/exe
>>>> even if /proc is not mounted. In the below example,
>>>> ./sh is a static shell binary:
>>>
>>> What if the user has procfs mounted somewherelse, what if they are in a
>>> chroot where you don't want them to patch the binary and re-exec it ?
>>>
>>> It would be far far cleaner for NOMMU to have a NOMMU private "reexec()"
>>> call that didn't rely on procfs or hacking names into the kernel.
>>>
>>> So NAK
>>
>> I am ok with it. Are other people ok with adding a syscall
>> just for this purpose? Al?
>
> please try a custom binfmt first

I did not understand you.
--
vda

  reply	other threads:[~2009-06-26 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 23:00 Denys Vlasenko
2009-06-24 23:21 ` Andrew Morton
2009-06-24 23:49   ` Denys Vlasenko
2009-06-24 14:51     ` Pavel Machek
2009-06-25  0:26     ` Andrew Morton
2009-06-26  8:06     ` Florian Weimer
2009-06-24 23:58 ` Al Viro
2009-06-25  0:07   ` Mike Frysinger
2009-06-26 23:18   ` Denys Vlasenko
2009-06-25  8:10 ` Alan Cox
2009-06-26  8:00   ` Denys Vlasenko
2009-06-26 13:26     ` Mike Frysinger
2009-06-26 22:55       ` Denys Vlasenko [this message]
2009-06-28 19:31         ` Mike Frysinger
2009-06-25 18:02 ` Eric W. Biederman
2009-06-25 18:16   ` Mike Frysinger

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=1158166a0906261555k3f00e9bdi74960e9eb72a4bb7@mail.gmail.com \
    --to=vda.linux@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®