Statically linking custom provider to libcrypto

[Dr Paul Dale]

You definitely don't want to follow the example set by the FIPS provider 
-- it is dynamic only.
Have a look at the OSSL_PROVIDER_add_builtin() call.


Pauli

On 25/1/23 17:57, Deividas Mozūraitis wrote:
> Dear OpenSSL users,
>
> 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.
>
> 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/build.info <http://build.info> and OpenSSL did compile a 
> bunch of object files from my providers source code, but it never 
> actually linked anything.
>
> Is there an easier way of doing this, or is this use case completely 
> unsupported and I should forget about it ?
>
> Thank you,
>
> Deividas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20230125/0878e3b6/attachment.htm>