Re: [openssl-dev] [openssl.org #4243] 1.1.0-pre2: bug: EVP_CIPHER_CTX isn't completely opaque

> This is according to our interpretation of "type opacity", meaning that the > type name is available but not its content. "Data hiding" is another way to p ut > it. This means that there will be a need to adapt, stack allocated > EVP_CIPHER_CTX is no longer allowed, but there are functions to

[openssl-dev] [openssl.org #4243] 1.1.0-pre2: bug: EVP_CIPHER_CTX isn't completely opaque

This is according to our interpretation of "type opacity", meaning that the type name is available but not its content. "Data hiding" is another way to put it. This means that there will be a need to adapt, stack allocated EVP_CIPHER_CTX is no longer allowed, but there are functions to allocate

[openssl-dev] [openssl.org #4243] 1.1.0-pre2: bug: EVP_CIPHER_CTX isn't completely opaque

hello, apologies if I am missing something here. There seems to be an inconsistency in 1.1.0-pre2 (didn't check -pre1). EVP_CIPHER_CTX is typedef'd in ossl_typ.h like this: typedef struct evp_cipher_ctx_st EVP_CIPHER_CTX; but struct evp_cipher_ctx_st isn't exposed any longer (it used to

Re: [openssl-dev] [openssl.org #4243] 1.1.0-pre2: bug: EVP_CIPHER_CTX isn't completely opaque

> On Jan 15, 2016, at 10:32 AM, baldu...@units.it via RT > wrote: > > This seems to be the reason why trying to build openssh-7.1p2 (with > -DOPENSSL_API_COMPAT=0x1000L) fails with: > >In file included from ssh_api.h:26:0, > from ssh_api.c:21: >

Re: [openssl-dev] [openssl.org #4243] 1.1.0-pre2: bug: EVP_CIPHER_CTX isn't completely opaque

> On Jan 15, 2016, at 10:32 AM, baldu...@units.it via RT > wrote: > > This seems to be the reason why trying to build openssh-7.1p2 (with > -DOPENSSL_API_COMPAT=0x1000L) fails with: > >In file included from ssh_api.h:26:0, > from ssh_api.c:21: >