On Tue, Apr 22, 2014 at 13:17, Vadim Lebedev wrote:
> I was alarmed by this:
>
> http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libssl/src/ssl/s3_clnt.c.diff?
> r1=1.34;r2=1.35;f=h
>
> Maybe i do misread something else but it seems like calls
> to OPENSSL_malloc/free routines are being replaced
Hi,
Vadim Lebedev wrote on Tue, Apr 22, 2014 at 01:17:16PM +:
> Theo de Raadt cvs.openbsd.org> writes:
>> Vadim Lebedev wrote:
>>> The removal of OPENSSL_malloc/OPENSSL_free ...
>>> etc will cause a LOT of pain
>> Which is why they are not removed.
> I was alarmed by this:
>
> http:
Theo de Raadt cvs.openbsd.org> writes:
>
> > The removal of OPENSSL_malloc/OPENSSL_free ...
> > etc will cause a LOT of pain
>
> Which is why they are not removed.
>
> > There is non négligeable number of
> > applications which are strongly depending on this functionality,
> > they us
> The removal of OPENSSL_malloc/OPENSSL_free ...
> etc will cause a LOT of pain
Which is why they are not removed.
> There is non négligeable number of
> applications which are strongly depending on this functionality,
> they use it for example to allocate SSL data structures in memory sh
On 22 April 2014 08:49, Vadim Lebedev wrote:
> Hello folks,
>
> The removal of OPENSSL_malloc/OPENSSL_free ...
> etc will cause a LOT of pain There is non négligeable number of
> applications which are strongly depending on this functionality,
> they use it for example to allocate SSL data st
Hello folks,
The removal of OPENSSL_malloc/OPENSSL_free ...
etc will cause a LOT of pain There is non négligeable number of
applications which are strongly depending on this functionality,
they use it for example to allocate SSL data structures in memory shared
between multiple forked ins
