Thanks, for whatever reason it caught the pbkdf2 stuff, not intensional.
I will update it asap
Jas
On Feb 17, 2013, at 3:12 AM, Stas Malyshev wrote:
> Hi!
>
>> The pull request addresses bug fix/feature request #38917 implementing
>> native signed public key & challenge support to the OpenSSL
On Apr 11, 2012, at 9:20 PM, Stas Malyshev wrote:
> Hi!
>
>> On that note Mr. Malyshev has indicated (in addition to several other
>> threads on the internals list) that no new features will be added in
>> 5.3 or 5.4 branches.
>
> 5.3 is out of the question, I think, but for 5.4 small self-cont
On Apr 11, 2012, at 8:39 PM, Yasuo Ohgaki wrote:
> Hi
>
> 2012/4/12 Stas Malyshev :
>> Hi!
>>
>>> There really doesn't seem to be much interest in this proposed patch.
>>> Should I continue development efforts on closing this feature request?
>>
>> Can't say anything here - I don't use these
On Apr 11, 2012, at 8:49 PM, Stas Malyshev wrote:
> Hi!
>
>> You might want to do something like
>>
>> USE_ZEND_ALLOC=0 ZEND_DONT_UNLOAD_MODULES=1
>> TEST_PHP_EXECUTABLE=./sapi/cli/php php ./run-tests.php -m ext/openssl/
I am glad I asked as I was not aware of this. Is there a comprehensive gu
There really doesn't seem to be much interest in this proposed patch. Should I
continue development efforts on closing this feature request?
I do also have a few questions regarding standards adherence, and memory leak
methods of detection.
I ask about the memory leak detection as passing test
+1
Not certain about a better solution but there are other methods of encrypting
and decrypting session data. In a recent project I have been tasked with
implementing a pdo stored procedure using mysql's aes functionality works well
with or without the patch. In a lot of ways I think that is th
