From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: mcgrof@gmail.com, zohar@linux.vnet.ibm.com, dwmw2@infradead.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] MODSIGN: Use PKCS#7 for module signatures [ver #7a]
Date: Wed, 12 Aug 2015 14:20:15 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1508121419410.5922@namei.org> (raw)
In-Reply-To: <15181.1439323425@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Tue, 11 Aug 2015, David Howells wrote:
> Hi James,
>
> Can you pull this into security/next please? Its aim is twofold: firstly,
> make the module signatures of PKCS#7/CMS format rather than a home-brewed
> format and secondly to pave the way for use of the signing code for
> firmware signatures (to follow later).
After installing the devel package, I now see these warnings and error:
WARNING: modpost: missing MODULE_LICENSE() in
crypto/asymmetric_keys/pkcs7_test_key.o
scripts/sign-file.c: In function ‘main’:
scripts/sign-file.c:188: warning: value computed is not used
At main.c:146:
- SSL error:02001002:system library:fopen:No such file or directory:
bss_file.c:169
- SSL error:2006D080:BIO routines:BIO_new_file:no such file:
bss_file.c:172
extract-cert: signing_key.pem: No such file or directory
rm: cannot remove `signing_key.x509': No such file or directory
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2015-08-12 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 20:03 David Howells
2015-08-12 4:20 ` James Morris [this message]
2015-08-12 7:07 ` David Woodhouse
2015-08-12 9:08 ` James Morris
2015-08-12 9:12 ` David Woodhouse
2015-08-12 9:27 ` James Morris
2015-08-12 9:50 ` David Woodhouse
2015-08-12 10:08 ` James Morris
2015-08-12 10:23 ` David Woodhouse
2015-08-12 10:30 ` James Morris
2015-08-12 10:40 ` James Morris
2015-08-12 10:59 ` David Woodhouse
2015-08-12 15:51 ` 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=alpine.LRH.2.20.1508121419410.5922@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=zohar@linux.vnet.ibm.com \
/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®