linux-kernel - Re: New mode DM-Verity error handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200618170952.GA18057@redhat.com>
Date:   Thu, 18 Jun 2020 13:09:52 -0400
From:   Mike Snitzer <snitzer@...hat.com>
To:     Sami Tolvanen <samitolvanen@...gle.com>
Cc:     JeongHyeon Lee <jhs2.lee@...sung.com>, dm-devel@...hat.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        agk@...hat.com, corbet@....net
Subject: Re: New mode DM-Verity error handling

On Thu, Jun 18 2020 at 12:50pm -0400,
Sami Tolvanen <samitolvanen@...gle.com> wrote:

> On Thu, Jun 18, 2020 at 11:44:45AM -0400, Mike Snitzer wrote:
> > I do not accept that panicing the system because of verity failure is
> > reasonable.
> > 
> > In fact, even rebooting (via DM_VERITY_MODE_RESTART) looks very wrong.
> > 
> > The device should be put in a failed state and left for admin recovery.
> 
> That's exactly how the restart mode works on some Android devices. The
> bootloader sees the verification error and puts the device in recovery
> mode. Using the restart mode on systems without firmware support won't
> make sense, obviously.

OK, so I need further justification from Samsung why they are asking for
this panic mode.

Thanks,
Mike