From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH v3 1/2] modules:capabilities: automatic module loading restriction Date: Wed, 19 Apr 2017 16:16:22 -0700 Message-ID: References: <1492640420-27345-1-git-send-email-tixxdz@gmail.com> <1492640420-27345-2-git-send-email-tixxdz@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1492640420-27345-2-git-send-email-tixxdz@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Djalal Harouni Cc: Linux Kernel Mailing List , Andy Lutomirski , Kees Cook , Andrew Morton , "Serge E. Hallyn" , "kernel-hardening@lists.openwall.com" , LSM List , Linux API , Dongsu Park , Casey Schaufler , James Morris , Paul Moore , Tetsuo Handa , Greg Kroah-Hartman , Jonathan Corbet , Jessica Yu , Rusty Russell , Arnaldo Carvalho de Melo List-Id: linux-api@vger.kernel.org On Wed, Apr 19, 2017 at 3:20 PM, Djalal Harouni wrote: > Currently, an explicit call to load or unload kernel modules require > CAP_SYS_MODULE capability. However unprivileged users have always been > able to load some modules using the implicit auto-load operation. An > automatic module loading happens when programs request a kernel feature > from a module that is not loaded. In order to satisfy userspace, the > kernel then automatically load all these required modules. I like this feature. --Andy