[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1olsHWnaEk6+b1L@kroah.com>
Date: Thu, 27 Oct 2022 08:31:12 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Casey Schaufler <casey@...aufler-ca.com>
Cc: casey.schaufler@...el.com, paul@...l-moore.com,
linux-security-module@...r.kernel.org, jmorris@...ei.org,
keescook@...omium.org, john.johansen@...onical.com,
penguin-kernel@...ove.sakura.ne.jp, stephen.smalley.work@...il.com,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
mic@...ikod.net
Subject: Re: [PATCH v1 2/8] LSM: Add an LSM identifier for external use
On Wed, Oct 26, 2022 at 12:36:34PM -0700, Casey Schaufler wrote:
> >> + *
> >> + * Copyright (C) 2022 Casey Schaufler <casey@...aufler-ca.com>
> >> + * Copyright (C) Intel Corporation
> > No date for Intel?
>
> The latest guidance I have received is that Intel does not want a date.
Ok, then I need to have an Intel lawyer sign off on a patch that does
this in order to have that be their official statement. Otherwise, it
needs a date.
> >> + */
> >> +
> >> +#ifndef _UAPI_LINUX_LSM_H
> >> +#define _UAPI_LINUX_LSM_H
> >> +
> >> +/*
> >> + * ID values to identify security modules.
> >> + * A system may use more than one security module.
> >> + *
> >> + * LSM_ID_XXX values 0 - 31 are reserved for future use
> > Reserved for what? Why?
>
> You're not the first person to ask.
And the answer is?
> I'll remove the reserved values for the next version.
Because we asked it will be removed?
confused,
greg k-h
Powered by blists - more mailing lists