ext/standard/crypt.c contains a whole bunch of #if's which, as I read it, won't
be very meaningful after 5.3.0,
where we provide our own implementations of any missing crypt() algorithms.
Most notably, automatic salt
generation, which I think will always use MD5 from now on?
Also, since blowfis
2009/6/28 Andrei Zmievski :
> Pierre Joye wrote:
>>
>> committed.
>
> I see that it's not in HEAD though, probably because HEAD has never been
> updated to use safe-allocation functions? I see no trace of __zend_calloc()
> there. We should probably port that from 5.3.
Yes, noticed that too while c
Hi Chris,
Thanks for the reply. I've only just got around to testing 5.2.10 final
on my dev server.
Andy,
It sounds like an infinite loop. If the problem persists, log a bug
at http://bugs.php.net/
I've noticed someone else has logged a bug and identified that it's a
conflict with the c
Pierre Joye wrote:
committed.
I see that it's not in HEAD though, probably because HEAD has never been updated to use
safe-allocation functions? I see no trace of __zend_calloc() there. We should probably
port that from 5.3.
-Andrei
--
PHP Internals - PHP Runtime Development Mailing List
T
committed.
2009/6/27 Johannes Schlüter :
> On Fri, 2009-06-26 at 14:23 -0700, Andrei Zmievski wrote:
>> I found what is effectively a memory corruption bug in all the branches.
>> pecalloc() uses
>> the wrong length to zero out the memory. Patch is attached, although I'm
>> somewhat
>> concerne
2009/6/27 Johannes Schlüter :
> On Fri, 2009-06-26 at 20:40 -0400, Ilia Alshanetsky wrote:
>> After some conversations with Rasmus on IRC i've come up with the
>> following patch:
>>
>> http://ilia.ws/patch/curl.txt
>
> I this the latest patch and all agree t it? Or were there further
> improvement
