On 31/07/2020 16:57, Emeric Brun wrote:
>
> Thanks! A lot to read!
>
> I have few questions:
>
> Do those changes have an impact on the external engine side API, specially
> for Async engines? The most used engine with my application is the Intel
> Quick Assist, in async mode.
>
> Does int
Hi Matt,
On 7/30/20 5:39 PM, Matt Caswell wrote:
>
>
> On 30/07/2020 16:06, Emeric Brun wrote:
>> Trying to compile my soft using openssl-3.0.0alpha5, I notice a lot of
>> warnings about deprecated ENGINE_* functions (since commit
>> 8dab4de53887639abc1152288fac76506beb87b3).
>>
>> Is-there an
Sounds like the pointer is *pointing to* memory containing 0x...
i.e. this is a use-after-free error.
You might consider building your app with Address Sanitizer enabled,
that might find the problem earlier during execution.
- Dan
On Fri, Jul 31, 2020 at 5:32 AM wrote:
> Hi guys,
>
>
>
Hi guys,
I've experienced the following strange behaviour.
I have the same code and the same openssl build.
With x64 everything I fine, but with x86 build not.
With a 32bit environment I got the following access vialotion.
I read that windows marks a freed pointer as "0X", but we are usall
On 31/07/2020 00:12, Thomas Dwyer III wrote:
> Is the result of EVP_default_properties_is_fips_enabled() supposed to
> take into account the default properties specified in the config file? I
> don't see it doing that. Also, regarding #11594, if default properties
> are currently still broken, w
