Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1646823
| From | Solar Designer <solar@openwall.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions |
| Date | 2017-05-22 14:20 +0200 |
| Message-ID | <tJUtA-5zo-27@gated-at.bofh.it> (permalink) |
| References | <tJUad-5dJ-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Alexander
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v4 next 0/3] modules: automatic module loading restrictions Djalal Harouni <tixxdz@gmail.com> - 2017-05-22 14:00 +0200
[PATCH v4 next 3/3] modules:capabilities: add a per-task modules auto-load mode Djalal Harouni <tixxdz@gmail.com> - 2017-05-22 14:00 +0200
Re: [PATCH v4 next 3/3] modules:capabilities: add a per-task modules auto-load mode kbuild test robot <lkp@intel.com> - 2017-05-23 16:20 +0200
[PATCH v4 next 2/3] modules:capabilities: automatic module loading restriction Djalal Harouni <tixxdz@gmail.com> - 2017-05-22 14:10 +0200
Re: [PATCH v4 next 2/3] modules:capabilities: automatic module loading restriction Kees Cook <keescook@chromium.org> - 2017-05-23 00:30 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Solar Designer <solar@openwall.com> - 2017-05-22 14:20 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Djalal Harouni <tixxdz@gmail.com> - 2017-05-22 15:50 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Solar Designer <solar@openwall.com> - 2017-05-22 18:50 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Djalal Harouni <tixxdz@gmail.com> - 2017-05-22 22:00 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Kees Cook <keescook@chromium.org> - 2017-05-23 01:10 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Andy Lutomirski <luto@kernel.org> - 2017-05-23 01:40 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Kees Cook <keescook@chromium.org> - 2017-05-23 02:00 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Djalal Harouni <tixxdz@gmail.com> - 2017-05-23 15:10 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Solar Designer <solar@openwall.com> - 2017-05-23 09:50 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Kees Cook <keescook@google.com> - 2017-05-23 20:40 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Andy Lutomirski <luto@kernel.org> - 2017-05-23 22:00 +0200
Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions Djalal Harouni <tixxdz@gmail.com> - 2017-05-24 20:10 +0200
csiph-web