linux-kernel - Re: [dm-devel] 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: <20200618165006.GA103290@google.com>
Date:   Thu, 18 Jun 2020 09:50:06 -0700
From:   Sami Tolvanen <samitolvanen@...gle.com>
To:     Mike Snitzer <snitzer@...hat.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: [dm-devel] New mode DM-Verity error handling

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.

Sami