All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Philipp Hahn <hahn@univention.de>,
	David Howells <dhowells@redhat.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Miscellaneous keyrings and modsign fixes
Date: Thu, 11 Feb 2016 08:35:44 -0500	[thread overview]
Message-ID: <56BC8E30.4010506@oracle.com> (raw)
In-Reply-To: <56BC423C.6080405@univention.de>

On 02/11/2016 03:11 AM, Philipp Hahn wrote:
> Hello David, cc:stable, cc:Sasha,
> 
> Am 25.09.2015 um 17:54 schrieb David Howells:
>> Can you pass these changes on to Linus?  There are four:
> ...
>>  (3) Don't strip leading zeros from the key ID when using it to construct a
>>      key description lest this make the key not match.
> 
> That commit e7c87bef7de2417b219d4dbfe8d33a0098a8df54 went into v4.3-rc4
> and is required to fix dd2f6c4481debfa389c1f2b2b1d5bd6449c42611, which
> was introduced with 3.18-rc1. As thus I recommend back-porting that fix
> and inclusion into
>  4.2
>  4.1
>  4.0
>  3.19
>  3.18
> The patch is simple enough to be cherry-picked into each branch without
> any fuzz.
> 
> We hit that bug and Ubuntu did too:
> <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1494943>

I've grabbed it for both 3.18 and 4.1.


Thanks,
Sasha

      parent reply	other threads:[~2016-02-11 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 15:54 [GIT PULL] Miscellaneous keyrings and modsign fixes David Howells
2015-09-29  9:17 ` James Morris
2015-09-29  9:17   ` James Morris
2016-02-11  8:11 ` Philipp Hahn
2016-02-11 11:41   ` David Howells
2016-02-11 13:35   ` Sasha Levin [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=56BC8E30.4010506@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=dhowells@redhat.com \
    --cc=hahn@univention.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.