linux-kernel - Re: [GIT PULL] KEYS: Changes for keyrings for security/next

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]

Date:	Mon, 22 Sep 2014 22:42:30 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	David Howells <dhowells@...hat.com>
cc:	keyrings@...ux-nfs.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KEYS: Changes for keyrings for security/next

On Mon, 22 Sep 2014, David Howells wrote:

> James Morris <jmorris@...ei.org> wrote:
> 
> > > Can you please pull these changes into security/next.  They include the fixes
> > > tag I previously requested as there's a dependency between these changes and
> > > the fixes.
> > > 
> > 
> > I'm getting this warning after pulling your code:
> > 
> >   CC      crypto/hash_info.o
> > crypto/asymmetric_keys/asymmetric_type.c: In function 
> > asymmetric_key_hex_to_key_id:
> > crypto/asymmetric_keys/asymmetric_type.c:110: warning: ignoring return 
> > value of hex2bin, declared with attribute warn_unused_result
> 
> I've posted an additional patch that moves some of the prevalidation to after
> the memory allocation in asymmetric_key_hex_to_key_id() and added it onto the
> keys-next branch.  Here's a revised pull request.
> ---
> Can you please pull these changes into security/next.  They include the fixes
> tag I previously requested as there's a dependency between these changes and
> the fixes.
> 

Ok, pulled to my next branch.


-- 
James Morris
<jmorris@...ei.org>

--
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/