[openssl-dev] procedure for adding new engine registration

[Vemulapalli Jyothi]

Hi Matt,

We could successfully execute dynamic engine support.
Thanks for help.

One issue regarding cleanup.
When I gone through openssl cleanup (ie apps_shutdown() or engine interface cleanup ) functionality, I see that there are two function pointers that can set to ENGINE interface: destroy and finish.

But after completion of openssl command execution or when invoking quit from openssl utility, these function pointers are not getting invoked.
In apps_shutdown(), I can see the call to ENGINE_cleanup(). But this cleanup is internal to openssl library. How can we set our engine de-init function pointer to openssl, where it should be invoked part of apps_shutdown() call. 

We are using openssl-1.0.1g version.

Can you please give us some data on this.

Thank you,
Jyothi



-----Original Message-----
From: openssl-dev [mailto:openssl-dev-bounces at openssl.org] On Behalf Of Matt Caswell
Sent: Friday, November 13, 2015 5:14 PM
To: openssl-dev at openssl.org
Subject: Re: [openssl-dev] procedure for adding new engine registration



On 13/11/15 11:16, Vemulapalli Jyothi wrote:
> Hi Matt,
> 
> Very useful information.
> 
> I too agree with you that we need not have a new engine distribution.
> 
> I see some options like dynamic engines and static engine support.
> 
> If we have built a library with dynamic engine interface, how can we do speed test using openssl speed command.

As follows (on Linux):

OPENSSL_ENGINES=/path/to/my/engine/dir openssl speed -engine myengine


Matt

_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev