[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssl-users
Subject:    Static vs dynamic engine configuration
From:       Brett Stahlman <brettstahlman () gmail ! com>
Date:       2020-10-26 19:01:28
Message-ID: CAOyxqKmmDghUVXBr9GUsK9tkFvP6cJ3=yHDhUvsiZu9a6P71-g () mail ! gmail ! com
[Download RAW message or body]

Hello,
I noticed that although the docs generally refer to the capi engine as
"builtin", it doesn't appear to be linked statically with openssl, and is
actually being loaded by the dynamic engine mechanism. I believe this is
because the OPENSSL_NO_STATIC_ENGINE flag is being set by Configure. The
only way I see to disable this flag is to pass disable-dynamic-engine to
Configure. Is this the correct way to get the builtin engines linked
statically? Do I understand correctly that dynamic loading of the builtin
engines is now the default?

Thanks,
Brett S.

[Attachment #3 (text/html)]

<div dir="ltr">Hello,<br><div>I noticed that although the docs generally refer to the \
capi engine as &quot;builtin&quot;, it doesn&#39;t appear to be linked statically \
with openssl, and is actually being loaded by the dynamic engine mechanism. I believe \
this is because the OPENSSL_NO_STATIC_ENGINE flag is being set by Configure. The only \
way I see to disable this flag is to pass disable-dynamic-engine to Configure. Is \
this the correct way to get the builtin engines linked statically? Do I understand \
correctly that dynamic loading of the builtin engines is now the \
default?</div><div><br></div><div>Thanks,</div><div>Brett S.</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]