ext/openssl: Add option to load legacy algorithm provider

OpenSSL 3.x relegated a set of insecure algorithms to a "legacy"
provider which is not loaded by default. Some of these algorith

ext/openssl: Add option to load legacy algorithm provider

OpenSSL 3.x relegated a set of insecure algorithms to a "legacy"
provider which is not loaded by default. Some of these algorithms
have utility beyond encryption such as for hashing, e.g., DES[1]

Add a compile-time option to load the legacy provider in 3.x. When
enabled, also load the default provider because loading any provider
explicitly disables auto-loading the default provider.

[1] https://github.com/vitessio/vitess/blob/9e40015748ede158357bd7291f583db138abc3df/go/vt/vtgate/vindexes/hash.go#L157

Closes GH-13951

show more ...

[ci skip] ext/sockets: followup on #14065. (#14066)

freebsd supports SO_NOSIGPIPE too.

ext/sockets: adding SO_NOSIGPIPE constant.

it s the macOs way to disable the SIGPIPE signal emission, same
as doing `signal(SIGPIPE, SIG_IGN)` but on the socket level.

Close GH

ext/sockets: adding SO_NOSIGPIPE constant.

it s the macOs way to disable the SIGPIPE signal emission, same
as doing `signal(SIGPIPE, SIG_IGN)` but on the socket level.

Close GH-14065

show more ...

Fix GH-13519: another attempt after the faulty fix.

Close GH-14055

ext/pcntl: signals list update for dragonflybsd related to checkpoint.

- SIGCKPT checkpoint and continue.
- SIGCKPTEXIT checkpoint and exit.

Close GH-14011

Fix GH-13727: Building with -Werror=strict-prototypes (#14029)

This is addon to the GH-13727 bug fix. When configuring the build with:

./configure CFLAGS=-Werror=strict-prototypes

Fix GH-13727: Building with -Werror=strict-prototypes (#14029)

This is addon to the GH-13727 bug fix. When configuring the build with:

./configure CFLAGS=-Werror=strict-prototypes

libtool check for parsing nm command would fail:

checking command to parse /usr/bin/nm -B output from cc object... failed

Upstream libtool has this specific check already fixed. Note that this
works only with Autoconf version 2.72 and later and is preparation for
future compilers that might have this error enabled by default.

show more ...

Temporary reset filename and lineno override before autoload

Closes GH-10232
Closes GH-13313

Fix erroneous dnl appended in configure (#14013)

This is a backport of commit 03f15534a17c7031b89dac7aaa21d59474517321 to
PHP-8.2 due to GH-14002 and fixes the PHP_CXX_COMPILE_STDCXX che

Fix erroneous dnl appended in configure (#14013)

This is a backport of commit 03f15534a17c7031b89dac7aaa21d59474517321 to
PHP-8.2 due to GH-14002 and fixes the PHP_CXX_COMPILE_STDCXX check in
ext/intl whether the specified C++ standard is mandatory or optional.

The `dnl` (Discard to Next Line) M4 macro in this combination of `m4_if`
macros and arguments isn't properly replaced and a literal `dnl` string
is appended in the configure script. The `[]dnl` works ok.

show more ...

NEWS

Closes GH-13782.

ext/session: fix _read/_write buffer limit.

MSDN pages mention the buffer size upper limit is INT_MAX not UINT_MAX.
inspired by GH-13205.

Close GH-14017

Fix GH-13998: Manage refcount of agg_context->val correctly (#14004)

When step_callback fails, agg_context->val is passed dtor, but agg_context->val
is also used in final_callback regard

Fix GH-13998: Manage refcount of agg_context->val correctly (#14004)

When step_callback fails, agg_context->val is passed dtor, but agg_context->val
is also used in final_callback regardless of the success/failure of step_callback,
so should not call dtor.

closes #14004
fixes #13998

show more ...

Fix missing handling of CALLABLE_CONVERT in cleanup_unfinished_calls()

Fixes GH-14003

Fix GH-13984: Buffer size is now checked before memcmp (#13991)

Fixed an issue where a buffer overflow occurred when a string shorter than
`:memory:` was passed as the db name of pdo_sql

Fix GH-13984: Buffer size is now checked before memcmp (#13991)

Fixed an issue where a buffer overflow occurred when a string shorter than
`:memory:` was passed as the db name of pdo_sqlite.

fixed #13984
closes #13991

show more ...

Add missing COMPILE_IGNORE_OTHER_FILES check for static calls

Closes GH-13986

[ci skip] NEWS

[ci skip] NEWS

ext/pcntl: pcntl_getqos_class/pcntl_setqos_class addition.

Introducting macOs Quality Of Service through those two calls.
on macOs arm64/M*, there is no concept of individual cores, thus

ext/pcntl: pcntl_getqos_class/pcntl_setqos_class addition.

Introducting macOs Quality Of Service through those two calls.
on macOs arm64/M*, there is no concept of individual cores, thus
the old thread policy for cpu affinity does not work here.
Instead, the user can apply to the current process the level of
performance/energy consumption they wish from the highest
QosClass::UserInteractive to QosClass::Background.

Close GH-13945

show more ...

Fix GH-13931: Applying zero offset to null pointer in Zend/zend_opcode.c

In the test cases, the compiler bails out due to a fatal error.
The data structures used by the compiler will con

Fix GH-13931: Applying zero offset to null pointer in Zend/zend_opcode.c

In the test cases, the compiler bails out due to a fatal error.
The data structures used by the compiler will contain stale values.
In particular, for the test case CG(loop_var_stack) will contain data.
The next compilation will incorrectly use elements from the previous
stack.
To solve this, we reset part of the compiler data structures.
We don't do a full re-initialization via init_compiler() because that will
also reset streams and resources.

Closes GH-13938.

show more ...

Fix file_get_contents() on Windows fails with "errno=22 Invalid argument"

Closes GH-13948

[ci skip] NEWS

News for GH-13041.

Include the source location in Closure names (#13550)

* Include the source location in Closure names

This change makes stack traces involving Closures, especially multiple
diffe

Include the source location in Closure names (#13550)

* Include the source location in Closure names

This change makes stack traces involving Closures, especially multiple
different Closures, much more useful, because it's more easily visible *which*
closure was called for a given stack frame.

The implementation is similar to that of anonymous classes which already
include the file name and line number within their generated classname.

* Update scripts/dev/bless_tests.php for closure naming

* Adjust existing tests for closure naming

* Adjust tests for closure naming that were not caught locally

* Drop the namespace from closure names

This is redundant with the included filename.

* Include filename and line number as separate keys in Closure debug info

* Fix test

* Fix test

* Include the surrounding class and function name in closure names

* Fix test

* Relax test expecations

* Fix tests after merge

* NEWS / UPGRADING

show more ...

Revert "ext/mysqlnd: support ER_CLIENT_INTERACTION_TIMEOUT"

This reverts commit 5035b8509016c4cf2cda883b4d3f245054a71626.

This broke Doctrine DBAL tests - more discussion in GH-1361

Revert "ext/mysqlnd: support ER_CLIENT_INTERACTION_TIMEOUT"

This reverts commit 5035b8509016c4cf2cda883b4d3f245054a71626.

This broke Doctrine DBAL tests - more discussion in GH-13618.

show more ...

ext/fileinfo/tests/bug78987.phpt: increase a memory limit

This test performs a few checks to ensure that "not too much" memory
is used while fileinfo is detecting encodings. It is howeve

ext/fileinfo/tests/bug78987.phpt: increase a memory limit

This test performs a few checks to ensure that "not too much" memory
is used while fileinfo is detecting encodings. It is however platform
specific, and memory usage varies across hosts and as libmagic changes.

Recently a Gentoo user reported a failure in this test at,

https://bugs.gentoo.org/927461

on a big-endian PPC64 machine with output,

---- EXPECTED OUTPUT
131072 => ok
262144 => ok
524288 => ok
1048576 => ok
2097152 => ok
4194304 => ok
8388608 => ok
16777216 => ok
---- ACTUAL OUTPUT
131072 => 10092544
262144 => 10092544
524288 => 12189696
1048576 => 12189696
2097152 => 14352384
4194304 => 18612224
8388608 => 24903680
16777216 => 37486592
---- FAILED

Those numbers are with 8.3.4 and therefore missing commit b7c5813c
which also raises the limits. Checking the "actual" numbers above
against the current values, we see that the limit for 524288 would
need to be bumped to 12189696 to allow this test to pass. Since that
seems reasonable, that's what this commit does.

Closes GH-13795
Closes GH-13940

show more ...

[ci skip] NEWS

[ci skip] NEWS