Re: [openssl-users] Loading engines recursively and crypto engine lock

On 10 August 2016 at 16:19, Jakob Bohm wrote: > On 10/08/2016 15:49, Krzysztof Konopko wrote: > >> On 10 August 2016 at 15:31, Jakob Bohm > jb-open...@wisemo.com>>wrote: >> ​ >> 1. Create a third engine3 which loads both engine1 and engine2 >> internally ( >> ​​ >> without going

Re: [openssl-users] Loading engines recursively and crypto engine lock

On 10/08/2016 15:49, Krzysztof Konopko wrote: On 10 August 2016 at 15:31, Jakob Bohm >wrote: I am not part of the OpenSSL team and have no idea what their thinking or suggestions are. ​Thanks for responding! ​ However the following should be a generi

Re: [openssl-users] Loading engines recursively and crypto engine lock

On 10 August 2016 at 15:31, Jakob Bohm wrote: > I am not part of the OpenSSL team and have no idea what their > thinking or suggestions are. > ​Thanks for responding! ​ > > However the following should be a generic workaround: > > 1. Create a third engine3 which loads both engine1 and engine2

Re: [openssl-users] Loading engines recursively and crypto engine lock

On 08/08/2016 13:39, Krzysztof Konopko wrote: Hi, TL;DR; Is it allowed to initialise engines recursively, ie. call `engine2->init` from `engine1->init`? -- I have a solution in a consumer product based on OpenSSL 1.0.2 series that uses two engines: one (engine1) for selecting client certif

[openssl-users] Loading engines recursively and crypto engine lock

Hi, TL;DR; Is it allowed to initialise engines recursively, ie. call `engine2->init` from `engine1->init`? -- I have a solution in a consumer product based on OpenSSL 1.0.2 series that uses two engines: one (engine1) for selecting client certificate chain (TLS client auth) and another one (engin