On Tue, 12 Feb 2019, Kees Cook wrote:
> To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
> used on the command line, and report that it is happening.
>
> Suggested-by: Tetsuo Handa
> Signed-off-by: Kees Cook
Applied to
On Sun, Feb 17, 2019 at 6:46 PM Paul Moore wrote:
> My main concern is that "selinux={0|1}" continues to work as it has
> for years. It doesn't look like this affects that, but I can't say
> I've dug into these changes very far.
Yup, no worries; it does. :)
--
Kees Cook
On Sun, Feb 17, 2019 at 12:17 AM Tetsuo Handa
wrote:
> On 2019/02/14 1:05, Casey Schaufler wrote:
> > On 2/12/2019 10:23 AM, Kees Cook wrote:
> >> To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
> >> used on the command line, and report that it is happening.
> >>
> >>
On 2019/02/14 1:05, Casey Schaufler wrote:
> On 2/12/2019 10:23 AM, Kees Cook wrote:
>> To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
>> used on the command line, and report that it is happening.
>>
>> Suggested-by: Tetsuo Handa
>> Signed-off-by: Kees Cook
>
>
On 2/12/2019 10:23 AM, Kees Cook wrote:
> To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
> used on the command line, and report that it is happening.
>
> Suggested-by: Tetsuo Handa
> Signed-off-by: Kees Cook
Acked-by: Casey Schaufler
> ---
>
To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
used on the command line, and report that it is happening.
Suggested-by: Tetsuo Handa
Signed-off-by: Kees Cook
---
Documentation/admin-guide/kernel-parameters.txt | 10 --
security/security.c
6 matches
Mail list logo
