linux-kernel - Module signing broken after SYSTEM_DATA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <186755.1440729515@turing-police.cc.vt.edu>
Date:	Thu, 27 Aug 2015 22:38:35 -0400
From:	Valdis Kletnieks <Valdis.Kletnieks@...edu>
To:	David Howells <dhowells@...hat.com>,
	David Woodhouse <David.Woodhouse@...el.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Module signing broken after SYSTEM_DATA_VERIFICATION commit?

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@...hat.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?

Content of type "application/pgp-signature" skipped