mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Heilman <jamie@audible.transient.net>
To: David Howells <dhowells@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)
Date: Sat, 30 Apr 2016 08:32:48 +0000	[thread overview]
Message-ID: <20160430083248.GA20775@cucamonga.audible.transient.net> (raw)

I usually build my kernels to require module signatures and use
automatic signing.  As of v4.6-rc1 I'm getting this on boot:

Problem loading in-kernel X.509 certificate (-2)

I bisected that to commit d43de6c780a84def056afaf4fb3e66bdaa1efc00
(akcipher: Move the RSA DER encoding check to the crypto layer)

For some reason after this commit my system keyring always ends up
empty.  I use the deb-pkg make target.  My kernel config can
be found at
http://audible.transient.net/~jamie/k/modsign.config-4.6.0-rc5-guest

Let me know if you need anything else.

-- 
Jamie Heilman                     http://audible.transient.net/~jamie/

             reply	other threads:[~2016-04-30  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-30  8:32 Jamie Heilman [this message]
2016-05-03  7:12 ` Herbert Xu
2016-05-03 17:26   ` Jamie Heilman
2016-05-03  8:54 ` David Howells
2016-05-03  9:10 ` David Howells
2016-05-03 17:25   ` Jamie Heilman
2016-05-03 20:35   ` David Howells
2016-05-03 20:55     ` Tadeusz Struk
2016-05-04  2:25       ` Jamie Heilman
2016-05-04  2:26     ` Jamie Heilman
2016-05-04  4:34       ` Tadeusz Struk
2016-05-04  4:53         ` Jamie Heilman
2016-05-04  9:01       ` David Howells
2016-05-04 13:38         ` Tadeusz Struk
2016-05-05  6:46           ` Herbert Xu

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=20160430083248.GA20775@cucamonga.audible.transient.net \
    --to=jamie@audible.transient.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®