Hello all,
I'm in process of porting our project to OpenSSL 1.1.0. We have part of
code which heavily uses M_ASN1_D2I_* and M_ASN1_I2D_* for defining d2i_*
and i2d_* methods for new extension. For example code uses M_ASN1_D2I_vars,
M_ASN1_D2I_Init and M_ASN1_D2I_start_sequence to start reading
Hi everyone,
i am working on my implementation of the engine that should be able to load
certificates. I was wondering is there any method that should perform such
a operation (like ENGINE_load_certificates if this method would exist).
Best regards
--
openssl-users mailing list
To unsubscribe:
Hello,
I appreciate if anyone can guide me how to set temporary EC Diffie-Hellman
parameters to be able to accept SSL connections from a client
using ephemeral ECDHE cipher.
I have an ssl based application that can accept SSL connections. I can
establish SSL connections from a client using RSA
On Wed, Sep 07, 2016, Daniel Knoppel wrote:
> Dear all,
>
> I was wondering about two things:
>
> 1. Can the EVP_Seal*() functions be told to use RSA_PKCS1_OAEP_PADDING,
> or do I need to stick with the lower level RSA_public_encrypt()?
>
> >From the source code it seems to me that
On Thu, Sep 08, 2016, Aleksandr Konstantinov wrote:
> Hello all,
>
> I'm in process of porting our project to OpenSSL 1.1.0. We have part of
> code which heavily uses M_ASN1_D2I_* and M_ASN1_I2D_* for defining d2i_*
> and i2d_* methods for new extension. For example code uses M_ASN1_D2I_vars,
>
Hello,
After I set a callback with X509_STORE_set_verify_cb(callback_fn), then
run:
X509_verify_cert( store_ctx, store, x509, untrusted )
Is it always true that store_ctx’s error state after X509_verify_cert()
will be identical to the final call into callback_fn()?
