From: Vitaly Chikunov <vt@altlinux.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH 1/4] ima-evm-utils: link to libcrypto instead of OpenSSL
Date: Fri, 12 Jul 2019 05:05:16 +0300 [thread overview]
Message-ID: <20190712020516.tpinh2xk43b6xufj@altlinux.org> (raw)
In-Reply-To: <20190711150732.7xrx42cnlsef6lit@altlinux.org>
Dmitry,
On Thu, Jul 11, 2019 at 06:07:32PM +0300, Vitaly Chikunov wrote:
> On Thu, May 23, 2019 at 03:26:20PM +0300, Dmitry Eremin-Solenikov wrote:
> > There is no need to link to full libssl. evmctl uses functions from
> > libcrypto, so let's link only against that library.
>
> Btw, this breaks my tests in my set up with gost-engine, making evmctl
> crash on OPENSSL_init_crypto (in bind_gost). Did not investigate real
> cause yet. I test with latest version of gost-engine (e372739) and
> openssl 0fc4d00a00.
Sorry, this was my set up failure. Previously I was defining
`OPENSSL_LIBS="-L$HOME/src/openssl -lssl -lcrypto"` to link with custom
OpenSSL build. Now I should just define
`LIBCRYPTO_LIBS="-L$HOME/src/openssl -lcrypto"` instead.
So there is no error in these commits.
Thanks,
prev parent reply other threads:[~2019-07-12 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:26 [PATCH 1/4] ima-evm-utils: link to libcrypto instead of OpenSSL Dmitry Eremin-Solenikov
2019-05-23 12:26 ` [PATCH 2/4] ima-evm-utils: replace INCLUDES with AM_CPPFLAGS Dmitry Eremin-Solenikov
2019-05-23 12:26 ` [PATCH 3/4] ima-evm-utils: include hash-info.gen into distribution Dmitry Eremin-Solenikov
2019-05-23 12:26 ` [PATCH 4/4] ima-evm-utils: update .gitignore files Dmitry Eremin-Solenikov
2019-05-23 15:12 ` [PATCH 1/4] ima-evm-utils: link to libcrypto instead of OpenSSL Mimi Zohar
2019-05-23 15:17 ` Dmitry Eremin-Solenikov
2019-07-11 15:07 ` Vitaly Chikunov
2019-07-12 2:05 ` Vitaly Chikunov [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=20190712020516.tpinh2xk43b6xufj@altlinux.org \
--to=vt@altlinux.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-integrity@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;
as well as URLs for NNTP newsgroup(s).