From: Dmitry Kasatkin <d.kasatkin@samsung.com>
To: David Howells <dhowells@redhat.com>
Cc: rusty@rustcorp.com.au, linux-security-module@vger.kernel.org,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Subject: Re: [PATCH 0/3] MODSIGN: Use PKCS#7 cert to avoid SKIDs
Date: Mon, 20 Oct 2014 14:12:01 +0300 [thread overview]
Message-ID: <5444EE01.6030005@samsung.com> (raw)
In-Reply-To: <1893.1413462701@warthog.procyon.org.uk>
On 16/10/14 15:31, David Howells wrote:
> Dmitry Kasatkin <d.kasatkin@samsung.com> wrote:
>
>> /tmp/ccgSFKJd.o: In function `display_openssl_errors':
>> sign-file.c:(.text+0x4e): undefined reference to `ERR_peek_error'
>> sign-file.c:(.text+0xa1): undefined reference to `ERR_error_string'
>> ...
> Is this solved for you by making the attached change?
>
> David
> ---
>
> diff --git a/scripts/Makefile b/scripts/Makefile
> index 1d9c40be606e..719311b7bd46 100644
> --- a/scripts/Makefile
> +++ b/scripts/Makefile
> @@ -20,7 +20,7 @@ hostprogs-$(CONFIG_MODULE_SIG) += sign-file
>
> HOSTCFLAGS_sortextable.o = -I$(srctree)/tools/include
> HOSTCFLAGS_asn1_compiler.o = -I$(srctree)/include
> -HOSTCFLAGS_sign-file.o = -lcrypto
> +HOSTLOADLIBES_sign-file = -lcrypto
>
Hi,
Yes. It helps...
- Dmitry
prev parent reply other threads:[~2014-10-20 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 14:30 [PATCH 0/3] MODSIGN: Use PKCS#7 cert to avoid SKIDs David Howells
2014-10-03 14:30 ` [PATCH 1/3] PKCS#7: Allow detached data to be supplied for signature checking purposes David Howells
2014-10-03 14:30 ` [PATCH 2/3] MODSIGN: Provide a utility to append a PKCS#7 signature to a module David Howells
2014-10-03 14:30 ` [PATCH 3/3] MODSIGN: Use PKCS#7 messages as module signatures David Howells
2014-10-06 14:19 ` [PATCH 0/3] MODSIGN: Use PKCS#7 cert to avoid SKIDs Dmitry Kasatkin
2014-10-16 12:31 ` David Howells
2014-10-20 11:12 ` Dmitry Kasatkin [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=5444EE01.6030005@samsung.com \
--to=d.kasatkin@samsung.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.