[openssl-users] Implementing ECDSA in an engine

[Reinier Torenbeek]

Hi Dmitry,

Thanks for the response. I suppose I have to do the same thing as well then.

I wonder why the ECDSA_METHOD structure and the associated mechanism to
insert it into an engine is so much different from the DSA_METHOD
struct. The latter seems more straightforward to use and does not
require the whole custom PKEY to be set up. Do you know?

Best regards,
Reinier

On 6/26/15 12:51 PM, Dmitry Belyavsky wrote:
> Hello Reinier, 
>
> On Fri, Jun 26, 2015 at 7:47 PM, Reinier Torenbeek
> <reinier.torenbeek at gmail.com <mailto:reinier.torenbeek at gmail.com>> wrote:
>
>     Hi,
>
>     The mechanism for implementing ECDSA in my own engine is unclear
>     to me.
>     Unfortunately, none of the example engines implement ECDSA so it
>     is hard
>     for me to find answers.
>
>     Invoking ENGINE_set_ECDSA() does not seem to be sufficient: my setup,
>     sign and verify methods never get invoked. Stepping through the
>     openssl
>     code, it looks like I also need to register my own EVP_PKEY_EC method.
>     That looks pretty complicated and I do not understand why that is
>     required in the first place if I only want to replace the ECDSA
>     signing
>     and verification methods.
>
>     Can someone confirm that registering my own EVP_PKEY_EC method is
>     indeed
>     the approach I have to take, or is there a shorter path to achieve
>     my goal?
>
>
> I did not find a way shorter then provide own EVP_PKEY_METHOD. But it
> works for me this way. 
>
> -- 
> SY, Dmitry Belyavsky
>
>
> _______________________________________________
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20150626/f0fd44f9/attachment.html>