In case I'm not the last to hear about it:
"Developers of the PHP programming language have identified two
critical vulnerabilities and have been urging website operators to run
an update to fix the issues.
The issue was first discovered using artificial intelligence, according
to a Google-owned cybersecurity agency.
PHP underpins large parts of the internet, raising concerns that a
significant number of websites could be vulnerable to attack.
Among those known to be affected are European government departments
and popular sites like Wikipedia." ...
https://www.abc.net.au/news/2026-10-22/php-vulnerabilities-cyber-asd/107294812
https://www.php.net/archive/2026.php#2026-10-21-5
You are it seems :D Patches/updated sources released around midnight Wed local, I finished updates here (cause we use the source, luke) around 6am Thu local (due the torrential weather alarms, I had been up since 430 anyway)
noel <deletethis@invalid.lan> wrote:
You are it seems :D Patches/updated sources released around midnight
Wed local, I finished updates here (cause we use the source, luke)
around 6am Thu local (due the torrential weather alarms, I had been up
since 430 anyway)
Debian still haven't sorted out how to apply them though. The updated
Debian 12 (Bookworm) and 13 (Trixie) PHP packages broke all sorts of
things because of this bug that stops PHP modules loading (as I posted
about in alt.os.linux.debian), which the maintainers sure are taking
their time looking into:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151659
Might be time for me to "use the source, Luke" too...
... sangoma are slack arses and dont use fast-cgi, just mod_php...
...but its far more memory efficient anyway than f/cgi which is I
guess why they stuck with it.
On Sun, 25 Oct 2026 11:24:02 +1000, Computer Nerd Kev wrote:
Debian still haven't sorted out how to apply them though. The updated
Debian 12 (Bookworm) and 13 (Trixie) PHP packages broke all sorts of
things because of this bug that stops PHP modules loading (as I posted
about in alt.os.linux.debian), which the maintainers sure are taking
their time looking into:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1151659
Might be time for me to "use the source, Luke" too...
on the one debian box i have that stays true to their repo, no sources,
is the freepbx 17 server, debian 12, I did not manualy update it, its
daily apt run did that, much closer to Thur midnight early Friday
It's fixed by running "apache2ctl stop", then "apache2ctl start",
instead of "apache2ctl restart". Or rebooting. Unfortunately Apache
probably remains vulnerable to PHP2Shell until you do that.
On 25 Oct 2026 20:24:55 +1000, noel wrote:
... sangoma are slack arses and dont use fast-cgi, just mod_php...
You mean PHP-FPM rather than FastCGI? PHP-FPM reimplements the entire (Apache-specific) mod_php environment within a standalone process,
using FastCGI to communicate with the web server. This allows PHP code written to run with mod_php to work with other web servers, so long as
they have FastCGI support.
As far as I know, nobody else uses FastCGI for anything.
...but its far more memory efficient anyway than f/cgi which is I guess
why they stuck with it.
Interesting to know ... but the right way to do things is to run yourcode in its own process anyway
Computer Nerd Kev wrote:
It's fixed by running "apache2ctl stop", then "apache2ctl start",
instead of "apache2ctl restart". Or rebooting. Unfortunately Apache
probably remains vulnerable to PHP2Shell until you do that.
I would expect restart to restart for something like that as apache will
not reload the newbie without it as you found out, i cant check reliably now, since freepbx had a few security updates that restarted the server,
but that was 18hrs after /shrug/
I see debian use their own custom apachectl, not the same as upstream but doesnt appear to do any harm at a quick look, just checked fpbx's php
info page, says 8.2.35 so is running correct mod_php
https://httpd.apache.org/docs/current/stopping.html#hup describes the
effect of this option:
apachectl -k restart
Sending the HUP or restart signal to the parent causes it to kill
off its children like in TERM, but the parent doesn't exit. It
re-reads its configuration files, and re-opens any log files. Then
it spawns a new set of children and continues serving hits.
i.e. in Apache speak, "restart" doesn't actually mean restarting the
server at all, at least in the common sense of restart meaning stop and
then start from scratch.
On Sun, 25 Oct 2026 20:23:28 +0000, Lawrence DrCOOliveiro wrote:
... the right way to do things is to run your code in its ownprocess anyway
Running a soho server might be fine, but if you try run that on
shared hosting servers, you just opened a new DoS vector exhausting
memory ...
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:49:09 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |