Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1376616
| From | James Morris <jmorris@namei.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 0/6] LSM: LoadPin for kernel file loading restrictions |
| Date | 2016-04-12 12:10 +0200 |
| Message-ID | <rn3qG-5Df-23@gated-at.bofh.it> (permalink) |
| References | <rl5ZD-3Ja-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, 6 Apr 2016, Kees Cook wrote: > This provides the mini-LSM "loadpin" that intercepts the now consolidated > kernel_file_read LSM hook so that a system can keep all loads coming from > a single trusted filesystem. This is what Chrome OS uses to pin kernel > module and firmware loading to the read-only crypto-verified dm-verity > partition so that kernel module signing is not needed. > This all looks good to me, just waiting now for the const fix suggested by Joe. -- James Morris <jmorris@namei.org>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v3 0/6] LSM: LoadPin for kernel file loading restrictions Kees Cook <keescook@chromium.org> - 2016-04-07 02:30 +0200
Re: [PATCH v3 0/6] LSM: LoadPin for kernel file loading restrictions James Morris <jmorris@namei.org> - 2016-04-12 12:10 +0200
Re: [PATCH v3 0/6] LSM: LoadPin for kernel file loading restrictions Kees Cook <keescook@chromium.org> - 2016-04-12 19:00 +0200
csiph-web