linux-kernel - Re: [patch] remove MNT_NOEXEC check for PROT

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]

Date:	Mon, 25 Sep 2006 00:22:06 +0400
From:	Stas Sergeev <stsp@...et.ru>
To:	Denis Vlasenko <vda.linux@...glemail.com>
Cc:	Ulrich Drepper <drepper@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Hugh Dickins <hugh@...itas.com>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] remove MNT_NOEXEC check for PROT_EXEC mmaps

Hello.

Denis Vlasenko wrote:
> If attacker has malicious loaders on the system,
> the situation is already sort of hopeless.
> Stas, I think noexec mounts are meant to prevent
> _accidental_ execution of binaries/libs from that
> filesystem.
In the past - yes. The problem is that this behaveour
was changed, which is this discussion all about.

> If user wants to execute binary blob from that fs
> bad enough, he will do it. Maybe just by
> copying file first to /tmp.
Not if you mount /tmp with noexec too. At least until
the loader script is written, which is probably some
time ahead. :)

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