lkml.org 
[lkml]   [2019]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH V32 01/27] Add the ability to lock down access to the running kernel image
From
Date
On 4/4/19 11:32 am, Matthew Garrett wrote:
> diff --git a/Documentation/ABI/testing/lockdown b/Documentation/ABI/testing/lockdown
> new file mode 100644
> index 000000000000..5bd51e20917a
> --- /dev/null
> +++ b/Documentation/ABI/testing/lockdown
> @@ -0,0 +1,19 @@
> +What: security/lockdown
> +Date: March 2019
> +Contact: Matthew Garrett <mjg59@google.com>
> +Description:
> + If CONFIG_LOCK_DOWN_KERNEL is enabled, the kernel can be
> + moved to a more locked down state at runtime by writing to
> + this attribute. Valid values are:
> +
> + integrity:
> + The kernel will disable functionality that allows
> + userland to modify the running kernel image, other
> + than through the loading or execution of appropriately
> + signed objects.
> +
> + confidentiality:
> + The kernel will disable all functionality disabled by
> + the integrity mode, but additionally will disable
> + features that potentially permit userland to obtain
> + confidential information stored within the kernel.

[+ linuxppc, mpe, dja, cmr]

I'm thinking about whether we should lock down the powerpc xmon debug
monitor - intuitively, I think the answer is yes if for no other reason
than Least Astonishment, when lockdown is enabled you probably don't
expect xmon to keep letting you access kernel memory.

Semantically though, xmon is not a userspace process - it's in kernel
and reads debug commands/outputs debug data directly from/to the
console. Is that a threat vector that this series cares about?


--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited

\
 
 \ /
  Last update: 2019-04-16 10:40    [W:0.130 / U:2.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site