is badly named. It
walks and
talks like a set0() but is called getm(). This is why I assumed, the pointers
may have
been filled by X509_SIG_new() and I'd be responsible for them.
--
Melvyn Sopacua
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi Stephen,
thank you for taking the time to answer.
On Saturday 25 February 2017 04:18:01 Dr. Stephen Henson wrote:
> On Sat, Jan 14, 2017, Melvyn Sopacua wrote:
> > This is caused by the code in [3].
> > That file also shows the problem: OpenSSL itself has access to
> >
encode_pkcs1(). But, I don't
see any way to setup the same context(s) from outside OpenSSL. There's
no X509_*_set_ to setup the algorithm and parameters.
Am I missing something or is it simply no longer possible to implement
these callbacks properly?
[1] https://github.com/melvyn-sop
