Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1647501
| From | Kees Cook <keescook@chromium.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] [PATCH v4 next 0/3] modules: automatic module loading restrictions |
| Date | 2017-05-23 02:00 +0200 |
| Message-ID | <tK5p0-3MF-13@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <tJVSG-6lF-11@gated-at.bofh.it> <tJYGR-86U-1@gated-at.bofh.it> <tK1EK-1rk-15@gated-at.bofh.it> <tK4CB-3wR-5@gated-at.bofh.it> <tK55D-3FX-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, May 22, 2017 at 4:38 PM, Andy Lutomirski <luto@kernel.org> wrote: > I think that having the un-resettable mode is unnecessary. We should > have option that disables loading modules entirely and cannot be > unset. (That means no explicit loads and not implicit loads.) Maybe > we already have this. Otherwise, tightening caps needed for implicit > loads should just be a normal yes/no setting IMO. Yup, /proc/sys/kernel/modules_disabled already does this. -- Kees Cook Pixel Security
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