[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b1507c1121b64b3abc00e154fcfeef65@huawei.com>
Date: Thu, 6 Feb 2020 09:36:40 +0000
From: Roberto Sassu <roberto.sassu@...wei.com>
To: Mimi Zohar <zohar@...ux.ibm.com>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>,
"jarkko.sakkinen@...ux.intel.com" <jarkko.sakkinen@...ux.intel.com>
CC: "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Silviu Vlasceanu <Silviu.Vlasceanu@...wei.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH v2 2/8] ima: Switch to ima_hash_algo for boot aggregate
> -----Original Message-----
> From: owner-linux-security-module@...r.kernel.org [mailto:owner-linux-
> security-module@...r.kernel.org] On Behalf Of Mimi Zohar
> Sent: Wednesday, February 5, 2020 10:01 PM
> To: Roberto Sassu <roberto.sassu@...wei.com>;
> James.Bottomley@...senPartnership.com;
> jarkko.sakkinen@...ux.intel.com
> Cc: linux-integrity@...r.kernel.org; linux-security-module@...r.kernel.org;
> linux-kernel@...r.kernel.org; Silviu Vlasceanu
> <Silviu.Vlasceanu@...wei.com>; stable@...r.kernel.org
> Subject: Re: [PATCH v2 2/8] ima: Switch to ima_hash_algo for boot
> aggregate
>
> Hi Roberto,
>
> On Wed, 2020-02-05 at 11:33 +0100, Roberto Sassu wrote:
>
> <snip>
>
> > Reported-by: Jerry Snitselaar <jsnitsel@...hat.com>
> > Suggested-by: James Bottomley
> <James.Bottomley@...senPartnership.com>
> > Signed-off-by: Roberto Sassu <roberto.sassu@...wei.com>
> > Cc: stable@...r.kernel.org
>
> Cc'ing stable resulted in Sasha's automated message. If you're going
> to Cc stable, then please include the stable kernel release (e.g. Cc:
> stable@...r.kernel.org # v5.3). Also please include a "Fixes" tag.
> Normally only bug fixes are backported.
Ok, will add the kernel version. I also thought which commit I should
mention in the Fixes tag. IMA always read the SHA1 bank from the
beginning. I could mention the patch that introduces the new API
to read other banks, but I'm not sure. What do you think?
Thanks
Roberto
Powered by blists - more mailing lists