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: Sat, 12 Dec 2020 17:21:19 -0800 From: Tushar Sugandhi <tusharsu@...ux.microsoft.com> To: Tyler Hicks <tyhicks@...ux.microsoft.com> Cc: zohar@...ux.ibm.com, stephen.smalley.work@...il.com, casey@...aufler-ca.com, agk@...hat.com, snitzer@...hat.com, gmazyland@...il.com, paul@...l-moore.com, sashal@...nel.org, jmorris@...ei.org, nramas@...ux.microsoft.com, linux-integrity@...r.kernel.org, selinux@...r.kernel.org, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, dm-devel@...hat.com Subject: Re: [PATCH v9 4/8] IMA: add policy rule to measure critical data On 2020-12-12 11:20 a.m., Tyler Hicks wrote: > On 2020-12-12 10:02:47, Tushar Sugandhi wrote: >> A new IMA policy rule is needed for the IMA hook >> ima_measure_critical_data() and the corresponding func CRITICAL_DATA for >> measuring the input buffer. The policy rule should ensure the buffer >> would get measured only when the policy rule allows the action. The >> policy rule should also support the necessary constraints (flags etc.) >> for integrity critical buffer data measurements. >> >> Add a policy rule to define the constraints for restricting integrity >> critical data measurements. >> >> Signed-off-by: Tushar Sugandhi <tusharsu@...ux.microsoft.com> > > This looks nice. Thanks for the changes! > > Reviewed-by: Tyler Hicks <tyhicks@...ux.microsoft.com> > > Tyler > Thanks for the detailed review on this series Tyler. We really appreciate it. ~Tushar
Powered by blists - more mailing lists