Fix #73530: Unsetting result set may reset other result set

Calling sqlite3_reset() when a result set object is freed can cause
undesired and maybe even hard to track interference with o

Fix #73530: Unsetting result set may reset other result set

Calling sqlite3_reset() when a result set object is freed can cause
undesired and maybe even hard to track interference with other result
sets. Furthermore, there is no need to call sqlite3_reset(), because
that is implicitly called on SQLite3Stmt::execute(), and users are
encouraged to explicitly call either SQLite3Result::finalize() or
SQLite3Stmt::reset() anyway.

show more ...

Fixed bug #69090 (check cached files permissions)

add missing NEWS entry

add missing NEWS entries

fix memory leak

Merge remote-tracking branch 'phpsec/PHP-5.6.28' into PHP-5.6

Fix bug #72776 (Invalid parameter in memcpy function trough openssl_pbkdf2)

add missing RETURN_STRINGL_CHECK

As RETVAL_STRINGL_CHECK is already there, this one is needed for
completion. One place in ext/bz2 is missing that, so it will likely
be useful for ot

add missing RETURN_STRINGL_CHECK

As RETVAL_STRINGL_CHECK is already there, this one is needed for
completion. One place in ext/bz2 is missing that, so it will likely
be useful for other possible fixes.

show more ...

fix dir separator in test

Add length check for bzcompress too - fix for bug #73356

More string length checks & fixes

Updated to version 2016.9 (2016i)

Fixed bug #73418 Integer Overflow in "_php_imap_mail" leads to crash

Fix #73436: Setting allow_url_fopen to Off makes several tests fail

We make sure that these tests run with allow_url_fopen=1.

Fix #72696: imagefilltoborder stackoverflow on truecolor images

We must not allow negative color values be passed to
gdImageFillToBorder(), because that can lead to infinite recursion

Fix #72696: imagefilltoborder stackoverflow on truecolor images

We must not allow negative color values be passed to
gdImageFillToBorder(), because that can lead to infinite recursion
since the recursion termination condition will not necessarily be met.

show more ...

Fix #72482: Ilegal write/read access caused by gdImageAALine overflow

Instead of rolling our own bounds check we use clip_1d() as it's done
in gdImageLine() and in external libgd. We mus

Fix #72482: Ilegal write/read access caused by gdImageAALine overflow

Instead of rolling our own bounds check we use clip_1d() as it's done
in gdImageLine() and in external libgd. We must not pass the image
width and height, respectively, but rather the largest ordinate value
that is allowed to be accessed, i.e. width-1 and height-1,
respectively.

show more ...

Fixed bug #73402 (Opcache segfault when using class constant to call a method)

5.6.29 will be next

Fix #72494: imagecropauto out-of-bounds access

This issue has actually already been fixed with commit 46f2c690. We're
adding a regression test and a NEWS entry, and also port the fix in

Fix #72494: imagecropauto out-of-bounds access

This issue has actually already been fixed with commit 46f2c690. We're
adding a regression test and a NEWS entry, and also port the fix in
gdImageCropThreshold() from libgd:
* <https://github.com/libgd/libgd/commit/b347e034>
* <https://github.com/libgd/libgd/commit/46f2c690>

show more ...

Updated to version 2016.8 (2016h)

Fix bug #73144 and bug #73341 - remove extra dtor

Fix bug #73331 - do not try to serialize/unserialize objects wddx can not handle

Proper soltion would be to call serialize/unserialize and deal with the result,
but this requires more wo

Fix bug #73331 - do not try to serialize/unserialize objects wddx can not handle

Proper soltion would be to call serialize/unserialize and deal with the result,
but this requires more work that should be done by wddx maintainer (not me).

show more ...

Fixed bug #73337 (try/catch not working with two exceptions inside a same operation)

Fix #73333: 2147483647 is fetched as string

We return all integers that can be represented as such by PHP as
integers, and only those that exceed the possible range as strings.
On bu

Fix #73333: 2147483647 is fetched as string

We return all integers that can be represented as such by PHP as
integers, and only those that exceed the possible range as strings.
On builds which represent integers with 64 bits, the range check is
unnecessary and might cause code checkers to complain, so we skip this
special casing via the preprocessor according to
<http://git.php.net/?p=php-src.git;a=commit;h=99d087e5>.

show more ...

use zend_error instead of zend_error_noreturn