Module signing broken after SYSTEM_DATA_VERIFICATION commit?

From	Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Newsgroups	linux.kernel
Subject	Module signing broken after SYSTEM_DATA_VERIFICATION commit?
Date	2015-08-28 04:40 +0200
Message-ID	<q2hK9-6Hs-1@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

I build kernels with MODULE_SIG=y, MODULE_SIG_FORCE=n (for build and run
coverage, but it shouldn't dork my system if it breaks). next-20150810
works just fine, but next-20150826 breaks modprobe - all calls to it
drop this in the dmesg:

[   31.829322] PKCS7: Unknown OID: [32] 2.16.840.1.101.3.4.2.3
[   31.829328] PKCS7: Unknown OID: [180] 2.16.840.1.101.3.4.2.3
[   31.829330] Unsupported digest algo: 55

and the modprobe fails.

This looks like the most suspicious commit in the area:

commit 091f6e26eb326adbd718f406e440c838bed8ebb6
Author: David Howells <dhowells@redhat.com>
Date:   Mon Jul 20 21:16:28 2015 +0100

    MODSIGN: Extract the blob PKCS#7 signature verifier from module signing

though it could be something else equally recent.  Is this ringing any
bells, or should I go bisect it?

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Module signing broken after SYSTEM_DATA_VERIFICATION commit? Valdis Kletnieks <Valdis.Kletnieks@vt.edu> - 2015-08-28 04:40 +0200
  Re: Module signing broken after SYSTEM_DATA_VERIFICATION commit? David Howells <dhowells@redhat.com> - 2015-08-28 12:20 +0200
  Re: Module signing broken after SYSTEM_DATA_VERIFICATION commit? David Howells <dhowells@redhat.com> - 2015-08-28 12:30 +0200
    Re: Module signing broken after SYSTEM_DATA_VERIFICATION commit? Valdis.Kletnieks@vt.edu - 2015-08-28 23:10 +0200

csiph-web