[openssl-users] M_ASN1_D2I_* replacement in OpenSSL 1.1.0

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 seq

[openssl-users] Using RSA_PKCS1_OAEP_PADDING with high level EVP_Seal functions

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 RSA_PKCS1_PADDING is hardcoded because EVP_SealInit() [1] calls EVP_PKEY_

Re: [openssl-users] [openssl-dev] dates, times, durations in next release (commands)

> Support RFC3339[1] is relative easy. But it's not enough, as folks are asking for the ability to specify durations. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users