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
| ||
|
Date: Tue, 11 Jun 2019 15:31:45 +1000 (AEST) From: James Morris <jmorris@...ei.org> To: Milan Broz <gmazyland@...il.com> cc: Jaskaran Khurana <jaskarankhurana@...ux.microsoft.com>, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org, linux-fsdevel@...r.kernel.org, agk@...hat.com, snitzer@...hat.com, dm-devel@...hat.com, scottsh@...rosoft.com, ebiggers@...gle.com, Mikulas Patocka <mpatocka@...hat.com> Subject: Re: [RFC PATCH v3 1/1] Add dm verity root hash pkcs7 sig validation On Sat, 8 Jun 2019, Milan Broz wrote: > > Adds DM_VERITY_VERIFY_ROOTHASH_SIG_FORCE: roothash signature *must* be > > specified for all dm verity volumes and verification must succeed prior > > to creation of device mapper block device. > > AFAIK there are tools that use dm-verity internally (some container > functions in systemd can recognize and check dm-verity partitions) and with > this option we will just kill possibility to use it without signature. > > Anyway, this is up to Mike and Mikulas, I guess generic distros will not > set this option. Right, I think this option would not be for a general purpose distro, but for embedded systems and other cases where the user may want a more tightly locked-down system. -- James Morris <jmorris@...ei.org>
Powered by blists - more mailing lists