linux-kernel - Re: Require mmap handler for a.out executables

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: <1154024752.13509.86.camel@localhost.localdomain>
Date:	Thu, 27 Jul 2006 19:25:52 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	7eggert@....de
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>, Eugene Teo <eteo@...hat.com>
Subject: Re: Require mmap handler for a.out executables

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)


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