All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@canonical.com>
To: David Howells <dhowells@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] x509: only prefix strip raw serial numbers
Date: Wed, 16 Sep 2015 11:57:51 +0100	[thread overview]
Message-ID: <20150916105751.GW19632@bark> (raw)
In-Reply-To: <10881.1442311183@warthog.procyon.org.uk>

On Tue, Sep 15, 2015 at 10:59:43AM +0100, David Howells wrote:
> Andy Whitcroft <apw@canonical.com> wrote:
> 
> > This leads us to truncate the id for kernel module signing keys and to
> > fail to recognise our own modules:
> > 
> >   [    1.572423] Loaded X.509 cert 'Build time autogenerated kernel
> >     key: 62a7c3d2da278be024da4af8652c071f3fea33'
> >   [    1.646153] Request for unknown module key 'Build time autogenerated
> >     kernel key: 0062a7c3d2da278be024da4af8652c071f3fea33' err -11
> 
> I don't suppose you've saved the key and a random small module that I can have
> a play with?

Sorry no, the key was an ephemeral key in those builds.  I did run a few
key builds to generate a new key with 0's to confirm this was possible.

> What version of the kernel are you using, btw?

Ahh yes, this was against a v4.2 final, I see that sign-file is all
changing to use openssl, so I will go confirm that this is not different
as a result.

-apw

  reply	other threads:[~2015-09-16 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  8:13 [PATCH 1/1] x509: only prefix strip raw serial numbers Andy Whitcroft
2015-09-15  9:59 ` David Howells
2015-09-16 10:57   ` Andy Whitcroft [this message]
2015-09-16 22:29 ` David Howells

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=20150916105751.GW19632@bark \
    --to=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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.