Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 22 May 2017 14:08:48 +0200
From: Solar Designer <>
To: Djalal Harouni <>
	Andy Lutomirski <>,
	Kees Cook <>,
	Andrew Morton <>,
	Rusty Russell <>,
	"Serge E. Hallyn" <>, Jessica Yu <>,
	"David S. Miller" <>,
	James Morris <>,
	Paul Moore <>,
	Stephen Smalley <>,
	Greg Kroah-Hartman <>,
	Tetsuo Handa <>,
	Ingo Molnar <>,
	Linux API <>,
	Dongsu Park <>,
	Casey Schaufler <>,
	Jonathan Corbet <>,
	Arnaldo Carvalho de Melo <>,
	Mauro Carvalho Chehab <>,
	Peter Zijlstra <>,
	Zendyani <>,,
	Al Viro <>,
	Ben Hutchings <>
Subject: Re: [PATCH v4 next 0/3] modules: automatic module loading restrictions

Hi Djalal,

Thank you for your work on this!

On Mon, May 22, 2017 at 01:57:03PM +0200, Djalal Harouni wrote:
> *) When modules_autoload_mode is set to (2), automatic module loading is
> disabled for all. Once set, this value can not be changed.

What purpose does this securelevel-like property ("Once set, this value
can not be changed.") serve here?  I think this mode 2 is needed, but
without this extra property, which is bypassable by e.g. explicitly
loaded kernel modules anyway (and that's OK).

I'm sorry if this has been discussed before.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.