linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: Still some race in X509 certificates handling
Date: Wed, 18 Feb 2015 15:36:45 +0100	[thread overview]
Message-ID: <54E4A37D.1040202@suse.cz> (raw)
In-Reply-To: <54E49BD2.1010503@suse.cz>

On 2015-02-18 15:04, Michal Marek wrote:
> On 2015-02-13 13:15, David Howells wrote:
>> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>>
>>> When it happens, I can do a rebuild, and the build will say
>>>
>>>    X.509 certificate list changed
>>>
>>> which is kind of odd, since the list should *always* be just that
>>> single key for me (ie "./signing_key.509").
>>
>> Did you by any chance set aside a build tree that went wrong?  If so, could
>> you have a look to see what's in:
>>
>> 	<builddir>/kernel/.x509.list
>> 	<builddir>/kernel/x509_certificate_list (note this is binary)
>> 	<builddir>/x509.genkey
>>
>> and make sure that:
>>
>> 	<builddir>/signing_key.priv
>> 	<builddir>/signing_key.x509
>>
>> both exist.  I wonder if the problem might perhaps be due to one of
>> signing_key.priv or signing_key.x509 getting removed somehow - but not both.
> 
> It could also be due to the usage of realpath when building the

Actually, I sent a patch for the "X.509 certificate list changed"
message last October: https://lkml.org/lkml/2014/10/8/306, please apply
it. However, this is just a spurious rebuild. The cause for the
signature verification error must be something else.

Michal

  reply	other threads:[~2015-02-18 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 18:18 Still some race in X509 certificates handling Linus Torvalds
2015-02-13 12:15 ` David Howells
2015-02-13 16:56   ` Linus Torvalds
2015-02-18 14:04   ` Michal Marek
2015-02-18 14:36     ` Michal Marek [this message]
2015-02-18 18:49       ` Linus Torvalds
2015-02-18 19:44         ` Michal Marek

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=54E4A37D.1040202@suse.cz \
    --to=mmarek@suse.cz \
    --cc=dhowells@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).