Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 27 Nov 2017 10:41:30 -0800
From: Linus Torvalds <>
To: Djalal Harouni <>
Cc: Kees Cook <>, Andy Lutomirski <>, 
	Andrew Morton <>, "Luis R. Rodriguez" <>, 
	James Morris <>, Ben Hutchings <>, 
	Solar Designer <>, Serge Hallyn <>, Jessica Yu <>, 
	Rusty Russell <>, 
	Linux Kernel Mailing List <>, 
	LSM List <>, 
	"" <>, Jonathan Corbet <>, 
	Ingo Molnar <>, "David S. Miller" <>, 
	Network Development <>, Peter Zijlstra <>
Subject: Re: [PATCH v5 next 0/5] Improve Module autoloading infrastructure

On Mon, Nov 27, 2017 at 9:18 AM, Djalal Harouni <> wrote:
> The sysctl flag is available at "/proc/sys/kernel/modules_autoload_mode"
> When modules_autoload_mode is set to (0), the default, there are no
> restrictions.

So quick question: do we actually need this?

Yes, it may be the current default, but is it anything that people
actually depend on?

I'd have expected that most module loading comes from system actions
anyway, not normal users.

So I'd like to explore first whether it even makes sense to make a new option.

New options are bad because:

 - opt-in security isn't security at all

 - having to configure things is complex

so we should generally strive to _not_ need new random config options.

What are the real life use-cases for normal users having modules auto-load?


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.