Re: Frustration with method based on EVP_PKEY_METHOD
OK. Thanks for replying. On Thu, 2010-07-08 at 18:59 +0200, Dr. Stephen Henson wrote: > The only current example of an external EVP_PKEY_METHOD (in the gost ENGINE) > implements everything from scratch. > > It is perfectly reasonable for another implementation to copy existing methods > or intercept them. The fact you can't do that with the current API is an > omission, sorry about that. I'll look into fixing that. > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org This email contains Morega Systems Inc. Privileged and Confidential information. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Frustration with method based on EVP_PKEY_METHOD
On Thu, Jul 08, 2010, Jeff Saremi wrote: > The structure itself is only forward-declared meaning that a programmer > has no way of getting into the actual evp_pkey_method_st and its fields. > Now that would be fine if there were a complete set of methods > EVP_PKEY_meth_* to manipulate the pointers to EVP_PKEY_METHOD. But alas > there's only a few. > For instance I cannot copy one struct to another meaning > EVP_PKEY_meth_copy() is missing. Note that we do have > EVP_PKEY_asn1_copy() which in many ways behaves the same way as its > counter part. > We can't also get a pointer to an existing function i.e. by calling > EVP_PKEY_meth_get_ctrl(). There are no "get" methods. > The only current example of an external EVP_PKEY_METHOD (in the gost ENGINE) implements everything from scratch. It is perfectly reasonable for another implementation to copy existing methods or intercept them. The fact you can't do that with the current API is an omission, sorry about that. I'll look into fixing that. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Frustration with method based on EVP_PKEY_METHOD
The structure itself is only forward-declared meaning that a programmer has no way of getting into the actual evp_pkey_method_st and its fields. Now that would be fine if there were a complete set of methods EVP_PKEY_meth_* to manipulate the pointers to EVP_PKEY_METHOD. But alas there's only a few. For instance I cannot copy one struct to another meaning EVP_PKEY_meth_copy() is missing. Note that we do have EVP_PKEY_asn1_copy() which in many ways behaves the same way as its counter part. We can't also get a pointer to an existing function i.e. by calling EVP_PKEY_meth_get_ctrl(). There are no "get" methods. If there's any rationale behind this, I'd love to know that. thanks jeff This email contains Morega Systems Inc. Privileged and Confidential information. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
