[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxoJcG5MN4OdaulL@redhat.com>
Date: Thu, 8 Sep 2022 11:25:36 -0400
From: Mike Snitzer <snitzer@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: agk@...hat.com, mka@...omium.org, dm-devel@...hat.com,
dianders@...omium.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, sarthakkukreti@...omium.org
Subject: Re: dm: verity-loadpin: Only trust verity targets with enforcement
On Wed, Sep 07 2022 at 6:34P -0400,
Kees Cook <keescook@...omium.org> wrote:
> On Wed, 7 Sep 2022 13:30:58 -0700, Matthias Kaehlcke wrote:
> > Verity targets can be configured to ignore corrupted data blocks.
> > LoadPin must only trust verity targets that are configured to
> > perform some kind of enforcement when data corruption is detected,
> > like returning an error, restarting the system or triggering a
> > panic.
> >
> >
> > [...]
>
> Applied to for-next/hardening, thanks!
>
> [1/1] dm: verity-loadpin: Only trust verity targets with enforcement
> https://git.kernel.org/kees/c/2e1875c05267
Does this mean you're intending to send this upstream? I prefer to
take all DM changes unless there is an external dependency.
Thanks,
Mike
Powered by blists - more mailing lists