On 04/26/18 16:37, Matt Caswell wrote:
On 26/04/18 21:17, Ken Goldman wrote:
I have to get the raw public modulus, but I cannot X509_get_pubkey()
because of a non-standard object identifier.
I can use X509_get_X509_PUBKEY() to get part way there. I see the DER
wrapped key in the public_key.d
On 26/04/18 21:17, Ken Goldman wrote:
> I have to get the raw public modulus, but I cannot X509_get_pubkey()
> because of a non-standard object identifier.
>
> I can use X509_get_X509_PUBKEY() to get part way there. I see the DER
> wrapped key in the public_key.data element, but I don't know an
I have to get the raw public modulus, but I cannot X509_get_pubkey()
because of a non-standard object identifier.
I can use X509_get_X509_PUBKEY() to get part way there. I see the DER
wrapped key in the public_key.data element, but I don't know an API to
get to that element.
Am I on the rig
We have not moved from OpenSSL 1.0.x to OpenSSL 1.1.x as we require the ability
to manually shutdown the library. We noticed in the latest release notes the
following:
"Modify compression code so it frees up structures without using the ex_data
callbacks. This works around a problem where some
Am 2018-03-29 09:07, schrieb Jan Kohnert:
Next update after clean test on another Win32 maschine: there have to
be crypt32.lib and ws2_32.lib libs linked, besides that the code is
unchanged. As the code produces correct asn1 files on Linux (see
previous mail), it now looks even more like a bug in
