From: Valdis.Kletnieks@vt.edu
To: David Howells <dhowells@redhat.com>
Cc: David Woodhouse <David.Woodhouse@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Module signing broken after SYSTEM_DATA_VERIFICATION commit?
Date: Fri, 28 Aug 2015 17:09:22 -0400 [thread overview]
Message-ID: <5375.1440796162@turing-police.cc.vt.edu> (raw)
In-Reply-To: <11332.1440757434@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Fri, 28 Aug 2015 11:23:54 +0100, David Howells said:
> Valdis Kletnieks <Valdis.Kletnieks@vt.edu> wrote:
>
> > [ 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
>
> OID_sha1, /* 1.3.14.3.2.26 */
> OID_sha256, /* 2.16.840.1.101.3.4.2.1 */
>
> I suspect I'm missing something here in oid_registry.h. Looking online, I
> see:
>
> id-sha256 OBJECT IDENTIFIER ::= { hashAlgs 1 }
> id-sha384 OBJECT IDENTIFIER ::= { hashAlgs 2 }
> id-sha512 OBJECT IDENTIFIER ::= { hashAlgs 3 }
> id-sha224 OBJECT IDENTIFIER ::= { hashAlgs 4 }
> id-sha512-224 OBJECT IDENTIFIER ::= { hashAlgs 5 }
> id-sha512-256 OBJECT IDENTIFIER ::= { hashAlgs 6 }
>
> Are you perchance using sha512 hashes in your signatures?
% grep MODULE_SIG /usr/src/linux-next/.config
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
CONFIG_MODULE_SIG_SHA512=y
CONFIG_MODULE_SIG_HASH="sha512"
CONFIG_MODULE_SIG_KEY="signing_key.pem"
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
prev parent reply other threads:[~2015-08-28 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 2:38 Valdis Kletnieks
2015-08-28 10:15 ` David Howells
2015-08-28 10:23 ` David Howells
2015-08-28 21:09 ` Valdis.Kletnieks [this message]
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=5375.1440796162@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=David.Woodhouse@intel.com \
--cc=dhowells@redhat.com \
--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®