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: <4528C0B0.4070002@aknet.ru>
Date:	Sun, 08 Oct 2006 13:11:12 +0400
From:	Stas Sergeev <stsp@...et.ru>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Ulrich Drepper <drepper@...hat.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jakub Jelinek <jakub@...hat.com>,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Hugh Dickins <hugh@...itas.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [patch] honour MNT_NOEXEC for access()

Hello.

Arjan van de Ven wrote:
>> but ld.so seems to be
>> the special case - it is a kernel helper after all,
> in what way is ld.so special in ANY way?
It is a kernel helper. Kernel does all the security
checks before invoking it. However, when invoked
directly, it have to do these checks itself. So it is
special in a way that it have to do the security checks
which otherwise only the kernel should do.
Otherwise, please tell me, how can you solve the problem
of ld.so started directly, can execute the files you do
not have an exec permission for? The MNT_NOEXEC hack of
mmap doesn't solve that.

Jeremy proposed playing with flags - interesting.
What if the MAP_EXECUTABLE flag, which is currently unused,
will be used for the program to explicitly specify that it
needs an exec permission on the file, and fail otherwise?
Then ld.so can just use that to solve all those permission
problems.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ