<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
You definitely don't want to follow the example set by the FIPS
provider -- it is dynamic only.<br>
Have a look at the OSSL_PROVIDER_add_builtin() call.<br>
<br>
<br>
Pauli<br>
<br>
<div class="moz-cite-prefix">On 25/1/23 17:57, Deividas MozĊĞraitis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKQk3-4BuAypBcWOgNuG40jaG3GZag=hoiF6twFrF2UZW01Q9A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Dear OpenSSL users,<br>
<br>
</div>
I've written a custom provider performing KEM and a
bunch of other operations. I compiled this provider
dynamically, loaded it in OpenSSL and it all works fine.
<br>
<br>
</div>
However, I have a requirement that the final product must
be a statically linked OpenSSL executable and
libcrypto/libssl. How can this be achieved ? I looked at
the source code and my guess is that I should try to mimic
how libfips is compiled, but I'm not exactly sure how the
OpenSSL build system works - I goofed around in providers/<a
href="http://build.info" moz-do-not-send="true">build.info</a>
and OpenSSL did compile a bunch of object files from my
providers source code, but it never actually linked
anything.<br>
<br>
</div>
Is there an easier way of doing this, or is this use case
completely unsupported and I should forget about it ?<br>
<br>
</div>
Thank you,<br>
<br>
</div>
Deividas<br>
</div>
</blockquote>
<br>
</body>
</html>