From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: d.kasatkin@samsung.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KEYS:
Date: Tue, 7 Oct 2014 15:58:15 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.11.1410071557590.7306@namei.org> (raw)
In-Reply-To: <4792.1412616356@warthog.procyon.org.uk>
On Mon, 6 Oct 2014, David Howells wrote:
> Hi James,
>
> Can you pull these fixes into your next branch?
>
> (1) Handle error codes in pointers correctly so as not to crash.
>
> (2) Fix the asymmetric key description to make module signature checking work
> right (I changed the description to include the X.509 serial number, but
> the module uses the subjectKeyId still).
>
> (3) Bring back matching of keys based on partial matches on the auxiliary
> IDs (required for IMA).
>
> (4) Make the PGP fingerprint field in /proc/keys hold the tail end of the
> SKID once again (if present).
>
> (5) IMA needs to zero-pad the key ID it requests a match on because the hex
> string will be rejected if it's not a multiple of two digits.
>
> David
> ---
> The following changes since commit c867d07e3c861e75509650b8a359351d634db93a:
>
> Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next (2014-10-02 19:47:23 +1000)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-next-fixes-20141006
Thanks, pulled.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2014-10-07 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 17:25 [GIT PULL] KEYS: David Howells
2014-10-07 4:58 ` James Morris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.11.1410071557590.7306@namei.org \
--to=jmorris@namei.org \
--cc=d.kasatkin@samsung.com \
--cc=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).