From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, 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 #7]
Date: Tue, 11 Aug 2015 03:13:00 +0100 [thread overview]
Message-ID: <6893.1439259180@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.20.1508111100380.24522@namei.org>
James Morris <jmorris@namei.org> wrote:
> On Mon, 10 Aug 2015, David Howells wrote:
>
> > James Morris <jmorris@namei.org> wrote:
> >
> > > I get a build failure:
> > >
> > > HOSTCC scripts/sign-file
> > > scripts/sign-file.c:20:25: error: openssl/bio.h: No such file or directory
> > >
> > > followed by many lines of error.
> >
> > What openssl do you have installed and do you have the -devel packages for it
> > installed? In particular libcrypto.
>
> openssl-1.0.1e-30.el6.11.x86_64
>
> and not the devel packages.
Yeah, you need the openssl-devel package now. There's some stuff using the
library directly allows us to do that you can't do with just the command line
tool.
This is mentioned in the
MODSIGN: Provide a utility to append a PKCS#7 signature to a module
commit description.
Note that the utility is written in C and must be linked against the
OpenSSL crypto library.
Would it help to update the module-signing.txt document, the config option or
the git pull request/cover note?
David
next prev parent reply other threads:[~2015-08-11 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 23:37 David Howells
2015-08-09 23:05 ` James Morris
2015-08-10 0:22 ` David Howells
2015-08-11 1:01 ` James Morris
2015-08-11 2:13 ` David Howells [this message]
2015-08-11 4:51 ` James Morris
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=6893.1439259180@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jmorris@namei.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
Powered by JetHome