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]

Message-ID: <4516BA95.6030900@aknet.ru>
Date:	Sun, 24 Sep 2006 21:04:21 +0400
From:	Stas Sergeev <stsp@...et.ru>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Hugh Dickins <hugh@...itas.com>, Andrew Morton <akpm@...l.org>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] remove MNT_NOEXEC check for PROT_EXEC mmaps

Hi.

Ulrich Drepper wrote:
> The consensus has been to add the same checks to mprotect.  They were
> not left out intentionally.
I know, and as long as the mmap have these checks,
that would be at least consistent.
But could you please explain what does that solve
*besides* the ld.so problem, which looks like the
user-space problem to me? I tried my best to express
the negative sides of that approach, but what are
the positive ones?
If that approach forces people to avoid using "noexec"
where they previously used it for good, then I'd even
call it a regression.

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