[openssl-dev] procedure for adding new engine registration

[Richard Levitte]

If your engine's 'destroy' isn't being invoked, you might want to have
a look at what ENGINE_remove() does, and ultimately,
engine_free_util() (found in crypto/engine/eng_lib.c).  Those should
be called as part of ENGINE_cleanup().

Cheers,
Richard

In message <BY1PR0301MB1238BBC6DA68672C825A070488E80 at BY1PR0301MB1238.namprd03.prod.outlook.com> on Wed, 9 Dec 2015 06:10:13 +0000, Vemulapalli Jyothi <jyothi.v at freescale.com> said:

jyothi.v> Hi Matt,
jyothi.v> 
jyothi.v> We could successfully execute dynamic engine support.
jyothi.v> Thanks for help.
jyothi.v> 
jyothi.v> One issue regarding cleanup.
jyothi.v> 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.
jyothi.v> 
jyothi.v> But after completion of openssl command execution or when invoking quit from openssl utility, these function pointers are not getting invoked.
jyothi.v> 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. 
jyothi.v> 
jyothi.v> We are using openssl-1.0.1g version.
jyothi.v> 
jyothi.v> Can you please give us some data on this.
jyothi.v> 
jyothi.v> Thank you,
jyothi.v> Jyothi
jyothi.v> 
jyothi.v> 
jyothi.v> 
jyothi.v> -----Original Message-----
jyothi.v> From: openssl-dev [mailto:openssl-dev-bounces at openssl.org] On Behalf Of Matt Caswell
jyothi.v> Sent: Friday, November 13, 2015 5:14 PM
jyothi.v> To: openssl-dev at openssl.org
jyothi.v> Subject: Re: [openssl-dev] procedure for adding new engine registration
jyothi.v> 
jyothi.v> 
jyothi.v> 
jyothi.v> On 13/11/15 11:16, Vemulapalli Jyothi wrote:
jyothi.v> > Hi Matt,
jyothi.v> > 
jyothi.v> > Very useful information.
jyothi.v> > 
jyothi.v> > I too agree with you that we need not have a new engine distribution.
jyothi.v> > 
jyothi.v> > I see some options like dynamic engines and static engine support.
jyothi.v> > 
jyothi.v> > If we have built a library with dynamic engine interface, how can we do speed test using openssl speed command.
jyothi.v> 
jyothi.v> As follows (on Linux):
jyothi.v> 
jyothi.v> OPENSSL_ENGINES=/path/to/my/engine/dir openssl speed -engine myengine
jyothi.v> 
jyothi.v> 
jyothi.v> Matt
jyothi.v> 
jyothi.v> _______________________________________________
jyothi.v> openssl-dev mailing list
jyothi.v> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
jyothi.v> _______________________________________________
jyothi.v> openssl-dev mailing list
jyothi.v> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
jyothi.v>