Update PHP... ASAP: php2shell was announced
Major (9.2 CVE) for PHP leaving all your PHP-backed apps vulnerable. Update right now. Make sure your version is 8.2 or greater as earlier ones are not supported (therefore not patched). Vulnerable versions from 5.x and later. https://sansec.io/research/php2shell
Thanks, Ron. Imagine my surprise to discover that, when checking as you suggested, I didn't have PHP even installed on my desktop, laptop or media/file server. (and I have quite a few server apps.) I seem to recall when PHP was trying to supplant perl and even shell scripting, it was everywhere. Now it appears a distant third behind Python and node.js -- sure it still powers the behemoths Wordpress and Drupal but doesn't seem to be at the heart of anything new. - Evan On Wed, Oct 21, 2026 at 11:07 AM Ron via Talk <talk@lists.gtalug.org> wrote:
Major (9.2 CVE) for PHP leaving all your PHP-backed apps vulnerable.
Update right now.
Make sure your version is 8.2 or greater as earlier ones are not supported (therefore not patched).
Vulnerable versions from 5.x and later.
https://sansec.io/research/php2shell ------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/EGUNXO4...
-- Evan Leibovitch, Toronto Canada @evanleibovitch / @el56
On Wed, Oct 21, 2026 at 08:49:15PM -0400, Evan Leibovitch via Talk wrote:
Imagine my surprise to discover that, when checking as you suggested, I didn't have PHP even installed on my desktop, laptop or media/file server. (and I have quite a few server apps.) I seem to recall when PHP was trying to supplant perl and even shell scripting, it was everywhere. Now it appears a distant third behind Python and node.js -- sure it still powers the behemoths Wordpress and Drupal but doesn't seem to be at the heart of anything new.
php was a lovely language to write code it, especially for web pages. The syntax was so obvious, it seemed you could just write what you thought it should be and you would almost always be right. Of course it had so many helpful features that it was incredibly easy to shoot yourself in the foot and make your code have big security holes. It was definitely designed for ease of use first, not security first. I would definitely not recommend using it and I certainly haven't used it in years. I wouldn't recommend using perl either. I am fine with python. -- Len Sorensen
On Oct 21, 2026, at 23:23, Lennart Sorensen via Talk <talk@lists.gtalug.org> wrote:
php was a lovely language to write code it, especially for web pages. The syntax was so obvious, it seemed you could just write what you thought it should be and you would almost always be right.
Of course it had so many helpful features that it was incredibly easy to shoot yourself in the foot and make your code have big security holes. It was definitely designed for ease of use first, not security first.
I would definitely not recommend using it and I certainly haven't used it in years.
PHP was advertised as being incredibly easy to program even for non-coders. Years ago Rasmus Lerdorf spoke at a TLUG meeting when he was introducing it, and someone pointed out you could do all the same things in Perl, to which Rasmus said that then you’d need to read a man page! Unfortunately a language anyone can write in led to reams of really bad code, and the mere fact something is written in PHP has become a code smell.
I wouldn't recommend using perl either. I am fine with python.
There are certainly too many languages. At one point about 20 years ago I was juggling C, C++, shell, Perl, PHP, and JavaScript, often jumping back and forth within projects, and sometimes the lowercase-with-semicolons dialects started to blur. I still love C but ought to learn Rust and Python. Anthony
On 2026-10-22 21:12, Anthony de Boer via Talk wrote:
On Oct 21, 2026, at 23:23, Lennart Sorensen via Talk <talk@lists.gtalug.org> wrote:
php was a lovely language to write code it, especially for web pages. The syntax was so obvious, it seemed you could just write what you thought it should be and you would almost always be right.
Of course it had so many helpful features that it was incredibly easy to shoot yourself in the foot and make your code have big security holes. It was definitely designed for ease of use first, not security first.
I would definitely not recommend using it and I certainly haven't used it in years.
PHP was advertised as being incredibly easy to program even for non-coders. Years ago Rasmus Lerdorf spoke at a TLUG meeting when he was introducing it, and someone pointed out you could do all the same things in Perl, to which Rasmus said that then you’d need to read a man page!
Unfortunately a language anyone can write in led to reams of really bad code, and the mere fact something is written in PHP has become a code smell.
I wouldn't recommend using perl either. I am fine with python.
There are certainly too many languages. At one point about 20 years ago I was juggling C, C++, shell, Perl, PHP, and JavaScript, often jumping back and forth within projects, and sometimes the lowercase-with-semicolons dialects started to blur. I still love C but ought to learn Rust and Python.
Anthony ------------------------------------
Alack and alas, I still like perl better than python though I code in each. I have some perl programs that I want to pass on to my son, who knows python but not perl. So I converted the perl to python. Here are the line counts and the character counts for each: wc -l taxcalc.* 1305 taxcalc.pl 2157 taxcalc.py ls -la taxcalc.* 64340 Sep 27 18:52 taxcalc.pl 77980 Sep 28 00:32 taxcalc.py time taxcalc.pl .... 1>/dev/null; real 0m0.070s time taxcalc.pl .... 1>/dev/null; real 0m0.073s The code implements the Federal/Ontario tax code, and I verify both programs output against the other, to the character, of output In truth, I don't find the python much easier to understand or code for, although I have to admit I am more proficient in perl than in python. In perl I do 'print "index $index \n"; in python I do `print(f"index {index}")` Which seems more straightforwards to you? -- Michael Galea
Reply is below quoted content. On Friday, October 23, 2026 1:25:01 a.m. Eastern Daylight Time Michael Galea via Talk wrote:
Alack and alas, I still like perl better than python though I code in each.
I have some perl programs that I want to pass on to my son, who knows python but not perl. So I converted the perl to python. Here are the line counts and the character counts for each: wc -l taxcalc.* 1305 taxcalc.pl 2157 taxcalc.py
ls -la taxcalc.* 64340 Sep 27 18:52 taxcalc.pl 77980 Sep 28 00:32 taxcalc.py
time taxcalc.pl .... 1>/dev/null; real 0m0.070s time taxcalc.pl .... 1>/dev/null; real 0m0.073s
The code implements the Federal/Ontario tax code, and I verify both programs output against the other, to the character, of output
In truth, I don't find the python much easier to understand or code for, although I have to admit I am more proficient in perl than in python. In perl I do 'print "index $index \n"; in python I do `print(f"index {index}")` Which seems more straightforwards to you?
-- Michael Galea
I would rather write 'say "index $index";'. With 'use 5.012' or so though. Syntax of Python is obviously more verbose and less flexible, and there is nothing other than 'print reverse <>' that better demonstrates the ability of Perl to take shortcuts. (But hold on, never pass it with untrusted arguments, otherwise it's arbitrary code execution) Well, and there are things like 'print (2+3)*2' or `use constant CONST => 'a'; print $hash{CONST}` which will likely behave in a way unexpected by those who are not very familiar with Perl. (Or something like https://github.com/karenetheridge/Tie-RefHash/commit/ 3dd3f18994f293307fff07be1d3a7e64e7d440df . I was able to spot the bug immediately upon seeing the code because I browsed metacpan / perldoc for fun) So to me both languages have strengths and weaknesses, for example Perl does not have explicit typing and booleans are painful (when you want to convert to/from something like JSON), and there is poor multithreading; while with Python one probably won't have the best experience writing many regular expressions, or trying to pass or return lambda functions. It really depends on the use case. Best regards, tusooa
On 2026-10-24 00:57, tusooa wrote:
Reply is below quoted content.
On Friday, October 23, 2026 1:25:01 a.m. Eastern Daylight Time Michael Galea via Talk wrote:
Alack and alas, I still like perl better than python though I code in each.
I have some perl programs that I want to pass on to my son, who knows python but not perl. So I converted the perl to python. Here are the line counts and the character counts for each: wc -l taxcalc.* 1305 taxcalc.pl 2157 taxcalc.py
ls -la taxcalc.* 64340 Sep 27 18:52 taxcalc.pl 77980 Sep 28 00:32 taxcalc.py
time taxcalc.pl .... 1>/dev/null; real 0m0.070s time taxcalc.pl .... 1>/dev/null; real 0m0.073s
The code implements the Federal/Ontario tax code, and I verify both programs output against the other, to the character, of output
In truth, I don't find the python much easier to understand or code for, although I have to admit I am more proficient in perl than in python. In perl I do 'print "index $index \n"; in python I do `print(f"index {index}")` Which seems more straightforwards to you?
-- Michael Galea
I would rather write 'say "index $index";'. With 'use 5.012' or so though.
Syntax of Python is obviously more verbose and less flexible, and there is nothing other than 'print reverse <>' that better demonstrates the ability of Perl to take shortcuts. (But hold on, never pass it with untrusted arguments, otherwise it's arbitrary code execution) Well, and there are things like 'print (2+3)*2' or `use constant CONST => 'a'; print $hash{CONST}` which will likely behave in a way unexpected by those who are not very familiar with Perl.
(Or something like https://github.com/karenetheridge/Tie-RefHash/commit/ 3dd3f18994f293307fff07be1d3a7e64e7d440df . I was able to spot the bug immediately upon seeing the code because I browsed metacpan / perldoc for fun)
So to me both languages have strengths and weaknesses, for example Perl does not have explicit typing and booleans are painful (when you want to convert to/from something like JSON), and there is poor multithreading; while with Python one probably won't have the best experience writing many regular expressions, or trying to pass or return lambda functions. It really depends on the use case.
Best regards, tusooa
Interesting. I use print rather than say, because I like my perl to look like C. I think that a world of issues that perl detractors posit, can be dealt with by restricting the language features and enforcing a clear style (perltidy is your friend).
------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/J562A37...
-- Michael Galea
On Fri, Oct 23, 2026 at 01:25:01AM -0400, Michael Galea via Talk wrote:
Alack and alas, I still like perl better than python though I code in each.
I have some perl programs that I want to pass on to my son, who knows python but not perl. So I converted the perl to python. Here are the line counts and the character counts for each: wc -l taxcalc.* 1305 taxcalc.pl 2157 taxcalc.py
ls -la taxcalc.* 64340 Sep 27 18:52 taxcalc.pl 77980 Sep 28 00:32 taxcalc.py
time taxcalc.pl .... 1>/dev/null; real 0m0.070s time taxcalc.pl .... 1>/dev/null; real 0m0.073s
The code implements the Federal/Ontario tax code, and I verify both programs output against the other, to the character, of output
In truth, I don't find the python much easier to understand or code for, although I have to admit I am more proficient in perl than in python. In perl I do 'print "index $index \n"; in python I do `print(f"index {index}")` Which seems more straightforwards to you?
I didn't like that print wasn't treated like a function in python 2.x. 3.x fixed that so it must be print(...). And I would use print("index %s" % (index)) because I guess I am still a C programmer at heart. -- Len Sorensen
From: Anthony de Boer via Talk <talk@lists.gtalug.org>
Unfortunately a language anyone can write in led to reams of really bad code, and the mere fact something is written in PHP has become a code smell.
Collective wisdom advances. Any old code is suspect. Code written by novices is also suspect. Large code bases are suspect. I've never used PHP, but my vague recollection is that it was very easy to use data from the wild in unsafe ways. Ways where metadata / commands could be smuggled in. For example, our understanding of buffer overflows has certainly advanced. Typical astonishing thing from the past: The IBM 1620 family of computers (introduced 1960) had a console typewriter. The machine language command to read from the console typewriter had no way to limit the length of the character sequence read. In fact, if the programmer got smart and made the buffer sit at the end of memory, the read command would allow the buffer to wrap around to the beginning of memory. Nothing was safe. AFAIK, nobody thought that this was surprising or dangerous. (From memory, I think that the command to read alphanumeric characters into location 1500 on would be 37 01500 00100. But I'm a bit rusty since I haven't used one of these beasts for about 50 years.)
On Fri, Oct 23, 2026 at 10:50:16AM -0400, D. Hugh Redelmeier wrote:
I've never used PHP, but my vague recollection is that it was very easy to use data from the wild in unsafe ways. Ways where metadata / commands could be smuggled in.
php used to allow include() statements to take a url as argument. That is disabled by default these days (config can still be changed to allow it). -- Len Sorensen
Its interesting, Dreamhost, where my employer's Ubuntu Linux shell is, updated ours to 8.5. A few months back in fact. However, I just discovered I am locked out of my ssh workspace, getting permission denied errors as if the password has been falsely changed. just wrote them, but still. Kare On Sat, 24 Oct 2026, Lennart Sorensen wrote:
On Fri, Oct 23, 2026 at 10:50:16AM -0400, D. Hugh Redelmeier wrote:
I've never used PHP, but my vague recollection is that it was very easy to use data from the wild in unsafe ways. Ways where metadata / commands could be smuggled in.
php used to allow include() statements to take a url as argument. That is disabled by default these days (config can still be changed to allow it).
-- Len Sorensen ------------------------------------ Description: GTALUG Talk Unsubscribe via Talk-unsubscribe@lists.gtalug.org Start a new thread: talk@lists.gtalug.org This message archived at https://lists.gtalug.org/archives/list/talk@lists.gtalug.org/message/BGP34IN...
participants (8)
-
Anthony de Boer -
D. Hugh Redelmeier -
Evan Leibovitch -
Karen Lewellen -
Lennart Sorensen -
Michael Galea -
Ron -
tusooa