linux-kernel - Re: [PATCH] dm verity: deferred hash checking for restart/logging mode

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 for Android: free password hash cracker in your pocket

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

Date:   Mon, 24 Apr 2017 08:54:08 -0700
From:   Sami Tolvanen <samitolvanen@...gle.com>
To:     Milan Broz <gmazyland@...il.com>
Cc:     Bongkyu Kim <bongkyu.kim@....com>, agk@...hat.com,
        snitzer@...hat.com, dm-devel@...hat.com, shli@...nel.org,
        linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
        Will Drewry <wad@...omium.org>
Subject: Re: [PATCH] dm verity: deferred hash checking for restart/logging
 mode

On Mon, Apr 24, 2017 at 10:05:03AM +0200, Milan Broz wrote:
> Isn't one of the goal of integrity checking to PREVENT that userspace
> accesses tampered data?

Absolutely. It's not acceptable for dm-verity to return unverified data
to userspace in restart mode.

Sami