Dear Richard, I am not sure it will not break the compatibility. Both implementations of the GOST ciphers require access to this field.
On Wed, Feb 17, 2016 at 12:42 PM, Richard Levitte via RT <r...@openssl.org> wrote: > Hi, > > I'm sorry, the oiv field is EVP private. Sure, it's been accessible (and > thoroughly misused in some cases) when EVP_CIPHER_CTX was open, but in > essence, > it's a EVP private store of the IV that was given at EVP_CipherInit(). > > If you want to retain a copy of the original IV, I suggest you have one in > GOSTs structure and take a copy of the IV given to the init() function. > > Thank you for the reminder, I meant to deal with this further. oiv should > really not be publically accessible at all, not even as a constant. > > Cheers, > Richard > > Vid Sat, 23 Jan 2016 kl. 09.40.19, skrev beld...@gmail.com: > > Hello, > > > > After making the EVP_CIPHER_CTX struct opaque I found that there is a > > missing non-const accessor to the oiv member. It is used in GOST engine > > when we set the cipher parameters from the ASN1 parameters. > > > > Thank you! > > > > > -- > Richard Levitte > levi...@openssl.org > > -- > Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4267 > Please log in as guest with password guest if prompted > > -- SY, Dmitry Belyavsky
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
