linux-kernel - Re: [GIT PULL] ima: bug fixes for Linus

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: <1385380993.2398.25.camel@dhcp-9-2-203-236.watson.ibm.com>
Date:	Mon, 25 Nov 2013 07:03:13 -0500
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	James Morris <jmorris@...ei.org>
Cc:	linux-security-module <linux-security-module@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] ima: bug fixes for Linus

On Mon, 2013-11-25 at 13:14 +1100, James Morris wrote:
> On Sun, 24 Nov 2013, Mimi Zohar wrote:
> 
> > On Mon, 2013-11-25 at 09:44 +1100, James Morris wrote:
> > > On Sun, 24 Nov 2013, Mimi Zohar wrote:
> > > 
> > > > Hi James,
> > > > 
> > > > Linus has already reverted the trusted keyring support for IMA patches.
> > > > These patches are re-based on -rc1.
> > > > 
> > > > The following changes since commit 4c1cc40a2d49500d84038ff751bc6cd183e729b5:
> > > > 
> > > >   Revert "KEYS: verify a certificate is signed by a 'trusted' key" (2013-11-23 16:38:17 -0800)
> > > > 
> > > > are available in the git repository at:
> > > > 
> > > >   git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity for-linus
> > > > 
> > > > for you to fetch changes up to 3eeb2d63ab623be55bb2ff584e123c0df45691e3:
> > > > 
> > > >   ima: make a copy of template_fmt in template_desc_init_fields() (2013-11-24 00:29:23 -0500)
> > > > 
> > > 
> > > I don't understand -- are these all fixes for regressions in the new 
> > > kernel?
> > 
> > Yes, mostly.  There's one code cleanup, that could be deferred and a
> > documentation update.
> 
> Can we leave documentation and code cleanups to the next cycle and only 
> include essential fixes for regressions at this stage?

Ok, all of the patches are needed and need to be upstreamed.  I assume
all of the ones that fix backwards compatibility issues would be termed
"essential fixes for regressions".

47a20c2 ima: do not include field length in template digest calc for ima templat
4c8f4bb ima: do not send field length to userspace for digest of ima template
3eeb2d6 ima: make a copy of template_fmt in template_desc_init_fields()

Could the remaining patches be marked for -stable?

> Also, please identify which upstream commits specifically are fixed by 
> each patch.

Ok

thanks,

Mimi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/