[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLtJt1=t7242gU22yf39p-96G+DhLspKEcAgA3q5AFxvQ@mail.gmail.com>
Date: Tue, 15 Aug 2017 17:29:38 -0700
From: Kees Cook <keescook@...omium.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Nick Kralevich <nnk@...gle.com>,
Sebastian Schmidt <yath@...h.de>,
Tony Luck <tony.luck@...el.com>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Patrick Tjin <pattjin@...gle.com>,
Mark Salyzyn <salyzyn@...gle.com>
Subject: Re: [PATCH 2/2] Revert "pstore: Honor dmesg_restrict sysctl on dmesg dumps"
On Tue, Aug 15, 2017 at 5:21 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 10 Aug 2017 13:36:35 -0700
> Kees Cook <keescook@...omium.org> wrote:
>
>> This reverts commit 68c4a4f8abc60c9440ede9cd123d48b78325f7a3, with
>> various conflict clean-ups.
>>
>> With the default root directory mode set to 0750 now, the capability
>> check was redundant.
>
> What's wrong with redundancy?
In this case, it actually _blocks_ system builders from being able to
define the access controls on pstore. :(
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists