public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: 7eggert@gmx.de
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Eugene Teo <eteo@redhat.com>
Subject: Re: Require mmap handler for a.out executables
Date: Thu, 27 Jul 2006 19:25:52 +0100	[thread overview]
Message-ID: <1154024752.13509.86.camel@localhost.localdomain> (raw)
In-Reply-To: <E1G69zn-0001Wb-66@be1.lrz>

Ar Iau, 2006-07-27 am 19:49 +0200, ysgrifennodd Bodo Eggert:
> Can shell scripts or binfmt_misc be exploited, too? Even if not, I'd
> additionally force noexec, nosuid on proc and sysfs mounts.

Why force them, this is just papering over imagined cracks and running
from shadows. If users want to be paranoid about these file systems or
their distro vendor is smart then the ability to set noexec/nosuid is
already supported and even more can be done with selinux. In fact as its
usually mounted in one place even AppArmor might be able to get it right
8)



  parent reply	other threads:[~2006-07-27 18:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6COYh-8f0-41@gated-at.bofh.it>
2006-07-27 17:49 ` Require mmap handler for a.out executables Bodo Eggert
2006-07-27 17:59   ` Eugene Teo
2006-07-27 18:25   ` Alan Cox [this message]
2006-07-27 21:18     ` Bodo Eggert
2006-07-26 10:31 Marcel Holtmann
2006-07-27 15:07 ` Christoph Hellwig
2006-07-27 15:18   ` Linus Torvalds
2006-07-27 15:44     ` Marcel Holtmann
2006-07-27 17:21   ` Eugene Teo

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=1154024752.13509.86.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=7eggert@gmx.de \
    --cc=akpm@osdl.org \
    --cc=eteo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=torvalds@osdl.org \
    /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