[EXTERNAL] Re: ENGINE API replacement for Openssl3.0

Petr Gotthard petr.gotthard at advantech.cz
Wed Sep 15 12:26:23 UTC 2021

you may also have a look at the https://github.com/provider-corner/vigenere
That's (as far as I know) the most simple provider implementation available.


-----Original Message-----
From: openssl-users <openssl-users-bounces at openssl.org> On Behalf Of Tomas Mraz
Sent: Wednesday, September 15, 2021 2:18 PM
To: Shivakumar Poojari <Shivakumar.Poojari at rbbn.com>; openssl-users at openssl.org
Cc: Paramashivaiah, Sunil <Sunil.Paramashivaiah at rbbn.com>; Bhattacharjee, Debapriyo (c) <dbhattacharjee at rbbn.com>
Subject: Re: [EXTERNAL] Re: ENGINE API replacement for Openssl3.0

I am sorry but as I said providers are not a direct replacement for ENGINEs. It is a completely different implementation of the same concept of pluggable cryptographical modules for OpenSSL. You can look at the OpenSSL manual pages for the providers.

This is the starting point:

There is no tutorial as for how to implement your own provider. And as I said on the application side if the application loads an OpenSSL configuration file the providers loaded can be configured via the config file and does not require any explicit API calls from the application.

I'd recommend looking at some of the test sources in the tests directory for some code examples.


On Wed, 2021-09-15 at 10:34 +0000, Shivakumar Poojari wrote:
> Hi Tomas,
> As Engine function are deprecated I tried using providers
> But how to use providers to get engine functionality tried in man 
> pages
> Some sample program will help, maybe some sample program will give the 
> clear idea how to use provider
> Struggling in understand the providers
> Please share the sample program and the links to understand the 
> providers
> Thanks,
> shiva kumar

More information about the openssl-users mailing list