rCyThis Is Not a DrillrCO: Critical PHP Vulnerabilities Are Setting the Internet on Fire
https://www.wired.com/story/this-is-not-a-drill-2-php-vulnerabilities-are-setting-the-internet-on-fire/
Just in case this impacts VMS shops.
Subcommandante XDelta <vlf@star.enet.dec.com> wrote:PHP on VMS is a mess.
rCyThis Is Not a DrillrCO: Critical PHP Vulnerabilities Are Setting the Internet on Fire
https://www.wired.com/story/this-is-not-a-drill-2-php-vulnerabilities-are-setting-the-internet-on-fire/
Just in case this impacts VMS shops.
It will. There is a VSI version of PHP out there are and it seems people
are using it. This is a very serious vulnerability although there is no exploit in the wild yet (and the VMS exploit is likely the last to be developed). But I'd hope that VSI is at work on patches to incorporate the fixes that were released yesterday.
On 10/22/2026 10:02 AM, Scott Dorsey wrote:Of course if one just like traditional PHP code and do
Subcommandante XDelta-a <vlf@star.enet.dec.com> wrote:PHP on VMS is a mess.
rCyThis Is Not a DrillrCO: Critical PHP Vulnerabilities Are Setting the >>> Internet on Fire
https://www.wired.com/story/this-is-not-a-drill-2-php-
vulnerabilities-are-setting-the-internet-on-fire/
Just in case this impacts VMS shops.
It will.-a There is a VSI version of PHP out there are and it seems people >> are using it.-a This is a very serious vulnerability although there is no
exploit in the wild yet (and the VMS exploit is likely the last to be
developed).-a But I'd hope that VSI is at work on patches to
incorporate the
fixes that were released yesterday.
VSI PHP is an ancient version (8.0!) and lacking extensions. I don't
know if VSI will patch. The patch may not be a trivial "grab from
upstream" as 8.0 is official EOL.
Berryman PHP is much better. I don't think he has released an update
yet.
Latest flavor is Issinoho PHP, which is on latest and greatest 8.5.
And he did release an updated version yesterday.
This is a very serious vulnerability although there is no
exploit in the wild yet (and the VMS exploit is likely the last to be developed).
PHP on VMS is a mess.
Subcommandante XDelta <vlf@star.enet.dec.com> wrote:
rCyThis Is Not a DrillrCO: Critical PHP Vulnerabilities Are Setting the Internet on Fire
https://www.wired.com/story/this-is-not-a-drill-2-php-vulnerabilities-are-setting-the-internet-on-fire/
Just in case this impacts VMS shops.
It will. There is a VSI version of PHP out there are and it seems people
are using it. This is a very serious vulnerability although there is no exploit in the wild yet
(and the VMS exploit is likely the last to be
developed).
On Thu, 22 Oct 2026 10:10:58 -0400, Arne Vajh|+j wrote:So why are they massively more successful than perl in their very
PHP on VMS is a mess.
s/ on VMS//
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But
they still donrCOt understand what theyrCOre copying.
Scott Dorsey <kludge@panix.com> wrote:Hopefully, majority of those interesting VMS web servers are serving
Subcommandante XDelta <vlf@star.enet.dec.com> wrote:
rCyThis Is Not a DrillrCO: Critical PHP Vulnerabilities Are Setting the >>Internet on Fire
https://www.wired.com/story/this-is-not-a-drill-2-php-vulnerabilities-are-setting-the-internet-on-fire/
Just in case this impacts VMS shops.
It will. There is a VSI version of PHP out there are and it seems
people are using it. This is a very serious vulnerability although
there is no exploit in the wild yet
That's right there with "this unexploded bomb is probably safe to play
with" ;-)
These days, given how fast we've seen AI tooling cobble together
exploits, it should be assumed that by the time a vulnerability is
known, exploits are out in the wild and used.
(and the VMS exploit is likely the last to be
developed).
Maybe. Although given that anything running OpenVMS these days is most
likely hosting something interesting (as opposed to a blog nobody
cares about), I'd not be surprised if the platform gets more
attention than previously.
Kind regards,
Alex.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
On Thu, 22 Oct 2026 10:10:58 -0400, Arne Vajh|+j wrote:
PHP on VMS is a mess.
s/ on VMS//
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But
they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
On Thu, 22 Oct 2026 10:10:58 -0400, Arne Vajhoj wrote:
PHP on VMS is a mess.
s/ on VMS//
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like they?ve moved on to trying to copy Python. But
they still don?t understand what they?re copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
On Fri, 23 Oct 2026 11:01:03 +0200
Alexander Schreiber <als@usenet.thangorodrim.de> wrote:
Maybe. Although given that anything running OpenVMS these days is most
likely hosting something interesting (as opposed to a blog nobody
cares about), I'd not be surprised if the platform gets more
attention than previously.
Hopefully, majority of those interesting VMS web servers are serving
various intranets rather than the Internet.
Or I am naive.
On 2026-10-23, Michael S <already5chosen@yahoo.com> wrote:Despite the CIO's favorite 100 slides PPT deck containing
Hopefully, majority of those interesting VMS web servers are serving
various intranets rather than the Internet.
Or I am naive.
I would hope that for something that important, those internal networks
are treated as potentially as hostile as those external networks.
This is the actual vulnerability writeup:It says:
https://www.wiz.io/blog/php2shell-php-rce
According to this writeup, only the last decade of releases are vulnerable.
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)ASP and PHP was widely successful because they were easy
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But
they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
This is a very serious vulnerability although there is no
exploit in the wild yet (and the VMS exploit is likely the last to be developed).
"No exploit in the wild" is incorrect.
https://aws.amazon.com/es/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
Meanwhile ...-a around 40% of all the worlds web sites are powered by Wordpress
On 10/23/2026 6:00 AM, Abandoned Trolley wrote:
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
Meanwhile ...-a around 40% of all the worlds web sites are powered by
Wordpress
WP is PHP.
On 23/10/2026 15:33, Arne Vajh|+j wrote:
On 10/23/2026 6:00 AM, Abandoned Trolley wrote:
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
Meanwhile ...-a around 40% of all the worlds web sites are powered by
Wordpress
WP is PHP.
thats the exact point I was trying to make :-\
drb@ihatespam.msu.edu (Dennis Boone) writes:
This is a very serious vulnerability although there is no
exploit in the wild yet (and the VMS exploit is likely the last to be
developed).
"No exploit in the wild" is incorrect.
https://aws.amazon.com/es/blogs/security/amazon-threat-intelligence-identifies-php2shell-exploitation-prior-to-public-disclosure-in-madpot/
They noted 'attempts to exploit'. As of yesterday, there had been no successful attempts to my knowledge.
In article <20261023123938.000065e7@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
On Thu, 22 Oct 2026 10:10:58 -0400, Arne Vajh|+j wrote:
PHP on VMS is a mess.
s/ on VMS//
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But >>> they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets. The syntax was clearly inspired by Perl,
which was popular at the time among the audience that PHP seemed
targeted for.
In product terms, PHP has been amazingly successful. From a
language design perspective, well...maybe not so much.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
Michael S <already5chosen@yahoo.com> wrote:
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until >>recently [in this niche] they were massively more successful than
python?
This is a very good question that I have been asking myself for years.
My guess would be that they are doing something right.
Clearly they are doing something right but it's clearly not anything technical.
On 2026-10-23, Scott Dorsey <kludge@panix.com> wrote:
Michael S <already5chosen@yahoo.com> wrote:
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
This is a very good question that I have been asking myself for years.
Because Perl is horrible to learn and use compared to PHP.
At a technical level, PHP is a horrible language but it is easy to learn.
It is the 21st century version of Visual Basic.
My guess would be that they are doing something right.
Clearly they are doing something right but it's clearly not anything
technical.
It wasn't about doing something right. They got lucky. They were able
to establish a large foothold in an empty market segment waiting to
be filled. Perl was starting in this segment, but it was far easier
for people to use PHP to fill this segment.
The PHP solutions now have the installed base advantage. Unfortunately.PHP is still rather unique with a low barrier to entry skill wise.
On 10/23/2026 5:39 AM, Michael S wrote:
ASP and PHP was widely successful because they were easy
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy
Perl, but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python.
But they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least
until recently [in this niche] they were massively more successful
than python?
My guess would be that they are doing something right.
to use.
In some ways the popularity has been both a blessing and
a curse for PHP.
Todays PHP is many things. There is a professional PHP segment using
Laravel, Symfony, Doctrine, Eloquent etc. powering many of the
worlds largest web sites.
On 10/23/26 07:51, Dan Cross wrote:
[snip]
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets. The syntax was clearly inspired by Perl,
which was popular at the time among the audience that PHP seemed
targeted for.
In product terms, PHP has been amazingly successful. From a
language design perspective, well...maybe not so much.
When I first saw PHP I saw a massive security problem. Sadly, people
still insisted on using it. Being retired I no longer have to spend my
time cleaning up for other peoples mistakes but I doubt that the
security behind PHP has improved.
On 10/23/2026 5:39 AM, Michael S wrote:
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But >>> they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
ASP and PHP was widely successful because they were easy
to use.
In article <nk1gv8F1eecU1@mid.individual.net>,
Bill Gunshannon <bill.gunshannon@gmail.com> wrote:
On 10/23/26 07:51, Dan Cross wrote:
[snip]
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets. The syntax was clearly inspired by Perl,
which was popular at the time among the audience that PHP seemed
targeted for.
In product terms, PHP has been amazingly successful. From a
language design perspective, well...maybe not so much.
When I first saw PHP I saw a massive security problem. Sadly, people
still insisted on using it. Being retired I no longer have to spend my
time cleaning up for other peoples mistakes but I doubt that the
security behind PHP has improved.
It feels a bit silly asking this now, but in what way? I mean,
what at the time stuck out as an obvious security hole?
On 10/23/26 17:11, Dan Cross wrote:
In article <nk1gv8F1eecU1@mid.individual.net>,I'll just throw out the one I saw abused the most.
Bill Gunshannon <bill.gunshannon@gmail.com> wrote:
On 10/23/26 07:51, Dan Cross wrote:
[snip]
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets. The syntax was clearly inspired by Perl,
which was popular at the time among the audience that PHP seemed
targeted for.
In product terms, PHP has been amazingly successful. From a
language design perspective, well...maybe not so much.
When I first saw PHP I saw a massive security problem. Sadly, people
still insisted on using it. Being retired I no longer have to spend my
time cleaning up for other peoples mistakes but I doubt that the
security behind PHP has improved.
It feels a bit silly asking this now, but in what way? I mean,
what at the time stuck out as an obvious security hole?
And, again, I am no longer involved maybe this went
away eventually but....
It was possible to get PHP to execute arbitrary commands
sent to it when it was used on the web. I saw people
from outside the university doing things like listing
directories and uploading files containing potentially
dangerous code.
And, no, I no longer have any of the examples. It was
possible to tighten security up to stop it but that also
stopped things the professors and students wanted to do.
I do not now and would never consider using PHP for anything.
In article <nk2bhaF5j2sU1@mid.individual.net>,
Bill Gunshannon <bill.gunshannon@gmail.com> wrote:
It was possible to get PHP to execute arbitrary commands
sent to it when it was used on the web. I saw people
from outside the university doing things like listing
directories and uploading files containing potentially
dangerous code.
And, no, I no longer have any of the examples. It was
possible to tighten security up to stop it but that also
stopped things the professors and students wanted to do.
I do not now and would never consider using PHP for anything.
With the disclaimer that I've never really used PHP other than
playing around once or twice, I kind of remember that it could
use backticks to perform command substitution, like Perl or a
Unix shell. My guess is that if user input had `cmd` in it and
was interpolated into a print statement or something without
escaping, it would run a command and interpolate the output
into whatever it printed.
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
Some simple examples:
1) Equality in PHP is loose equality "==" by default. You have to use
"===" to get strict equality. This leads to warnings like this scattered throughout the PHP manual: (See the Return Values section.)
https://www.php.net/manual/en/function.fgetc.php
This is a great source of subtle errors. I don't like to see PHP code
that uses loose equality for this reason.
2) Things that should be errors are warnings and execution continues by default unless you make the error reporting level more strict in your
code. I always use strict error reporting when I have to use PHP for
this reason.
3) mysqli_real_escape_string() doesn't always work:It always works as documented and intended.
https://www.php.net/manual/en/mysqli.real-escape-string.php
(See the Warning: section)
On 2026-10-23, Dan Cross <cross@spitfire.i.gajendra.net> wrote:
In article <nk2bhaF5j2sU1@mid.individual.net>,
Bill Gunshannon <bill.gunshannon@gmail.com> wrote:
It was possible to get PHP to execute arbitrary commands
sent to it when it was used on the web. I saw people
from outside the university doing things like listing
directories and uploading files containing potentially
dangerous code.
And, no, I no longer have any of the examples. It was
possible to tighten security up to stop it but that also
stopped things the professors and students wanted to do.
I do not now and would never consider using PHP for anything.
With the disclaimer that I've never really used PHP other than
playing around once or twice, I kind of remember that it could
use backticks to perform command substitution, like Perl or a
Unix shell. My guess is that if user input had `cmd` in it and
was interpolated into a print statement or something without
escaping, it would run a command and interpolate the output
into whatever it printed.
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
You are correct Dan that it had to be a programming error for that
to happen (it was not some builtin feature of PHP) but it is also
_way_ too easy to make silly programming errors in PHP.
Some simple examples:
1) Equality in PHP is loose equality "==" by default. [...]
2) Things that should be errors are warnings and execution continues by >default unless you make the error reporting level more strict in your
code. I always use strict error reporting when I have to use PHP for
this reason.
3) mysqli_real_escape_string() doesn't always work: [...]
In article <20261023123938.000065e7@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But >>> they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets.
The early web was a mess. The protocol was hugely wasteful; theNo doubt that the switch from CGI to ASP and PHP changed
markup language was anemic, and people were resorting to all
kinds of bad ideas to try and build content (constructing forms
from tables, for example, so that boxes could be aligned). The
web had coalesced around an example from a book with a single
addition, but like a high-school kegger, the word got out and it
quickly got out of hand. A lot of non-technical people were
authoring web pages and web sites by writing HTML directly.
They didn't _want_ to become programmers.
CFML, ASP, and PHP stepped into that world and filled a bit of a
void. It inverted the model; you weren't writing programs to
generate markup guided by the program's behavior, you were
injecting behavior by embedding little snippets of programs in
your markup. The design-oriented types who wanted to focus on
content could largely do that. I don't think that has to be
inherently insecure, though I can see how having someone around
to add a bit of domain expertise to the mix can prevent a lot of
problems down the road. Textual interpolation is a powerful
tool; so is a chainsaw. Both can do a lot of damage.
On 10/23/26 17:11, Dan Cross wrote:
In article <nk1gv8F1eecU1@mid.individual.net>,I'll just throw out the one I saw abused the most.
Bill Gunshannon-a <bill.gunshannon@gmail.com> wrote:
When I first saw PHP I saw a massive security problem.-a Sadly, people
still insisted on using it.-a Being retired I no longer have to spend my >>> time cleaning up for other peoples mistakes but I doubt that the
security behind PHP has improved.
It feels a bit silly asking this now, but in what way?-a I mean,
what at the time stuck out as an obvious security hole?
And, again, I am no longer involved maybe this went
away eventually but....
It was possible to get PHP to execute arbitrary commands
sent to it when it was used on the web.
I saw people
from outside the university doing things like listing
directories and uploading files containing potentially
dangerous code.
With the disclaimer that I've never really used PHP other than
playing around once or twice, I kind of remember that it could
use backticks to perform command substitution, like Perl or a
Unix shell. My guess is that if user input had `cmd` in it and
was interpolated into a print statement or something without
escaping, it would run a command and interpolate the output
into whatever it printed.
It's probably true that a language like PHP shouldn't have thatPractically every technology provide a way to execute external
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
The early web was a mess. The protocol was hugely wasteful; the
markup language was anemic, and people were resorting to all
kinds of bad ideas to try and build content (constructing forms
from tables, for example, so that boxes could be aligned). The
web had coalesced around an example from a book with a single
addition, but like a high-school kegger, the word got out and it
quickly got out of hand. A lot of non-technical people were
authoring web pages and web sites by writing HTML directly.
They didn't _want_ to become programmers.
On 10/23/2026 5:11 PM, Dan Cross wrote:
The early web was a mess. The protocol was hugely wasteful; the
markup language was anemic, and people were resorting to all
kinds of bad ideas to try and build content (constructing forms
from tables, for example, so that boxes could be aligned). The
web had coalesced around an example from a book with a single
addition, but like a high-school kegger, the word got out and it
quickly got out of hand. A lot of non-technical people were
authoring web pages and web sites by writing HTML directly.
They didn't _want_ to become programmers.
CFML, ASP, and PHP stepped into that world and filled a bit of a
void. It inverted the model; you weren't writing programs to
generate markup guided by the program's behavior, you were
injecting behavior by embedding little snippets of programs in
your markup. The design-oriented types who wanted to focus on
content could largely do that. I don't think that has to be
inherently insecure, though I can see how having someone around
to add a bit of domain expertise to the mix can prevent a lot of
problems down the road. Textual interpolation is a powerful
tool; so is a chainsaw. Both can do a lot of damage.
No doubt that the switch from CGI to ASP and PHP changed
who could and who did make dynamic web pages.
But at the core ASP and PHP are really just a way to
save a gazillion "response write".
Here is super simple example of DCL CGI:
$ write sys$output "content-type: text/html"
$ write sys$output ""
$ write sys$output "<html>"
$ write sys$output "<head>"
$ write sys$output "<title>Show time</title>"
$ write sys$output "</head>"
$ write sys$output "<body>"
$ write sys$output "<h1>Show time</h1>"
$ write sys$output "<p>"
$ write sys$output "Time is " + f$time() + "."
$ write sys$output "</p>"
$ write sys$output "</body>"
$ write sys$output "</html>"
$ exit
(I chose DCL because with my Perl skills I would
not bother the Perl gurus here with my way of writing
Perl)
[snip]
The interesting part is what happens under the hood. JSP
pages are not interpreted - they are compiled. Or more
precisely: they are triple compiled. The JSP compiler
compiles from JSP to Java source, the Java compiler
compiles from Java source to Java byte code and the
JVM JIT compiles from Java byte code to native code.
In article <11bivpt$305om$1@dont-email.me>,DCL can add text blocks as well. But without symbol
Arne Vajh|+j <arne@vajhoej.dk> wrote:
Here is super simple example of DCL CGI:
$ write sys$output "content-type: text/html"
$ write sys$output ""
$ write sys$output "<html>"
$ write sys$output "<head>"
$ write sys$output "<title>Show time</title>"
$ write sys$output "</head>"
$ write sys$output "<body>"
$ write sys$output "<h1>Show time</h1>"
$ write sys$output "<p>"
$ write sys$output "Time is " + f$time() + "."
$ write sys$output "</p>"
$ write sys$output "</body>"
$ write sys$output "</html>"
$ exit
I guess Perl could use a "HERE" document for that:
#!/usr/bin/perl
use warnings;
use strict;
use POSIX qw(strftime);
my $now = uc strftime "%d-%b-%Y %T", localtime;
print <<"EOF";
<html>
<head>
<title>Show time</title>
</head>
<body>
<h1>Show time</h1>
Time is $now.
</body>
</html>
EOF
(I chose DCL because with my Perl skills I would
not bother the Perl gurus here with my way of writing
Perl)
"There's more than one way to do it!"
On 10/23/2026 7:51 AM, Dan Cross wrote:
In article <20261023123938.000065e7@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But >>>> they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets.
I suspect that demand created multiple similar solutions.
PHP 1.0 : 08-Jun-1995
ColdFusion 1.0 : 10-Jul-1995 [different sources have different dates but >they all say July]
ASP 1.0 : 10-Dec-1996
Note that CFML typical use tags not script snippets. So in that
regard it is more like JSP with JSTL and ASP.NET web forms than
like PHP, ASP and JSP without JSTL. Or to put it differently: CFML
was 7 years ahead of the rest.
On 10/23/2026 9:59 PM, Dan Cross wrote:
With the disclaimer that I've never really used PHP other than
playing around once or twice, I kind of remember that it could
use backticks to perform command substitution, like Perl or a
Unix shell. My guess is that if user input had `cmd` in it and
was interpolated into a print statement or something without
escaping, it would run a command and interpolate the output
into whatever it printed.
Backticks can be used as short form for calling shell_exec.
$ type dan.php
<?php
$cmd = 'show def';
echo "bla `$cmd` bla\n";
$dd1 = shell_exec($cmd);
echo $dd1;
$dd2 = `$cmd`;
echo $dd2;
$ php dan.php
bla `show def` bla
DISK2:[ARNE]
DISK2:[ARNE]
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
Practically every technology provide a way to execute external
commands.
Having a short form like PHP backticks is probably unique.
But it is really just a shell_exec call.
And of course input to that type of function should be checked.
[snip]
DCL can add text blocks as well. But without symbol
substiution.
Always === is a good workaround.
First note that the recommended way to use mysqli is to use prepare. mysqli_real_escape_string only exist for extraordinary
circumstances.
But there is a reason that the function is called escape
and not escape_and_quote - it just escapes - it does not quote.
PHP mysqli_real_escape_string put backslashes in front of
problematic characters.
But at the core ASP and PHP are really just a way to save a
gazillion "response write".
Having a short form like PHP backticks is probably unique.
On Sat, 24 Oct 2026 11:59:30 -0400, Arne Vajh|+j wrote:
First note that the recommended way to use mysqli is to use prepare.
mysqli_real_escape_string only exist for extraordinary
circumstances.
What do you use for LIKE and REGEXP clauses?
PHP mysqli_real_escape_string put backslashes in front of
problematic characters.
Note that backslash-escapes are not standard SQL.
Two good rules:But there is a reason that the function is called escape
and not escape_and_quote - it just escapes - it does not quote.
You need a function that turns an object in the application language
into an appropriate literal in the query language, including quotes
where appropriate but leaving them out if not. For example, whatever
in your language maps to rCLNULLrCY in SQL must never be quoted!
For example, hererCOs function IrCOve been using in Python code, that
does strictly standard SQL quoting:
def sql_string(s) :
"returns an SQL string literal that evaluates to s."
if s == None :
q = "null"
elif isinstance(s, int) :
q = "%d" % s
elif isinstance(s, (bytes, bytearray)) :
q = "X'" + "".join("%02x" % d for d in s) + "'"
elif isinstance(s, str) :
q = "'" + s.replace("'", "''") + "'"
else :
raise TypeError("can only convert bytes, str, int or None types")
#end if
return q
#end sql_string
On Fri, 23 Oct 2026 10:23:16 -0400, Arne Vajh|+j wrote:
Todays PHP is many things. There is a professional PHP segment using
Laravel, Symfony, Doctrine, Eloquent etc. powering many of the
worlds largest web sites.
Most or all of those are still built around the strict
one-page-per-file request/response model. They canrCOt handle
WebSockets, just for example.
Or basic background tasks, that might
need to run independently of page requests from users.
In article <11biu7b$2vhq4$1@dont-email.me>,Wikipedia PHP article has the same example.
Arne Vajh|+j <arne@vajhoej.dk> wrote:
PHP 1.0 : 08-Jun-1995
ColdFusion 1.0 : 10-Jul-1995 [different sources have different dates but
they all say July]
ASP 1.0 : 10-Dec-1996
The PHP of June 1995 did not look like the PHP one sees today.
The history at https://www.php.net/manual/en/history.php.php
describes the evolution and gives an example of PHP/FI 2.0 circa
1997/1998; it is very different. That page says that PHP 3.0 is
the first version that's clearly related to the modern language.
In article <11bj186$30n6f$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/23/2026 9:59 PM, Dan Cross wrote:
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
Practically every technology provide a way to execute external
commands.
Indeed, but the danger isn't the mechanism, it is the specific implementation. PHP is very often used to build applications
that are exposed to all kinds of untrusted inputs. Backticks in
an environment where much input is untrusted, for example, seem
unnecessarily permissive.
term% phpeval is another function that need to be very strictly controlled.
<?php
$cmd='`pwd`';
echo $cmd;
eval("echo $cmd;");
`pwd`/home/cross
term%
Sure, its a cheat to use `eval` here, but maybe interpolation of
backticks should not be allowed anywhere except an assignment,
and perhaps PHP shouldn't have an `eval`.
PHP applications often do web sockets.
Does not seem to be a problem in the real world.
The simple rule for starting background tasks directly in
web applications is: don't do it.
test("BB\\' or 1=1 #")--- Synchronet 3.22a-Linux NewsLink 1.2
On 10/24/2026 6:43 PM, Lawrence DrCOOliveiro wrote:
Note that backslash-escapes are not standard SQL.
What do you use for LIKE and REGEXP clauses?
prepare of course.
In article <11bivpt$305om$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
The interesting part is what happens under the hood. JSP
pages are not interpreted - they are compiled. Or more
precisely: they are triple compiled. The JSP compiler
compiles from JSP to Java source, the Java compiler
compiles from Java source to Java byte code and the
JVM JIT compiles from Java byte code to native code.
It may be relevant to point out that PHP is basically a compiled
to a bespoke virtual machine (Zend) at this point; the old days
of a slow, simple interpreter are long gone.
Facebook came up; it was (in)?famously written in PHPHack is how Facebook think PHP 7.x & 8.x should have been.
originally, but some may be familiar with the "Hack" language
they developed that introdcued gradual typing for it; they also
have a bespoke VM ("Hip Hop") that runs it. I doubt they care
*too* much about what happens in the mainstream PHP world.
On 10/24/2026 5:04 PM, Dan Cross wrote:
In article <11bj186$30n6f$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/23/2026 9:59 PM, Dan Cross wrote:
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
Practically every technology provide a way to execute external
commands.
Indeed, but the danger isn't the mechanism, it is the specific
implementation. PHP is very often used to build applications
that are exposed to all kinds of untrusted inputs. Backticks in
an environment where much input is untrusted, for example, seem
unnecessarily permissive.
Almost all languages has the capability including languages
used for web.
Even if Bill write CGI script in VMS Cobol he could call LIB$SPAWN.
And unlike many other languages then it easy to block in PHP.
Just add:
disable_functions = shell_exec
to php.ini and it is gone.
term% php
<?php
$cmd='`pwd`';
echo $cmd;
eval("echo $cmd;");
`pwd`/home/cross
term%
Sure, its a cheat to use `eval` here, but maybe interpolation of
backticks should not be allowed anywhere except an assignment,
and perhaps PHP shouldn't have an `eval`.
eval is another function that need to be very strictly controlled.
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
On Sat, 24 Oct 2026 19:46:12 -0400, Arne Vajh|+j wrote:
What do you use for LIKE and REGEXP clauses?
prepare of course.
You mean, mysqli_stmt_prepare()? You think this will work?
mysqli_stmt_prepare(-2stmt-+, "select -2table-+ from -2table-+ where -2field-+ like \"%?%\"")
?
On 10/24/2026 3:42 PM, Dan Cross wrote:
In article <11bivpt$305om$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
The interesting part is what happens under the hood. JSP
pages are not interpreted - they are compiled. Or more
precisely: they are triple compiled. The JSP compiler
compiles from JSP to Java source, the Java compiler
compiles from Java source to Java byte code and the
JVM JIT compiles from Java byte code to native code.
It may be relevant to point out that PHP is basically a compiled
to a bespoke virtual machine (Zend) at this point; the old days
of a slow, simple interpreter are long gone.
The traditional Zend engine is like traditional CPython:
convert the source to an intermediate byte code and
interpret that.
Performance is interpreter like not JIT compiler like.
Zend added some JIT in 8.0 and CPython in 3.13.
CPython JIT is a joke performance wise.
Zend JIT may be a little better.
Facebook came up; it was (in)?famously written in PHPHack is how Facebook think PHP 7.x & 8.x should have been.
originally, but some may be familiar with the "Hack" language
they developed that introdcued gradual typing for it; they also
have a bespoke VM ("Hip Hop") that runs it. I doubt they care
*too* much about what happens in the mainstream PHP world.
Funny enough given where this discussion started, then it
does not support mixing of code and HTML - it is all code.
HHVM JIT compiles. And is pretty good at it.
And just to complete: PeachPie on CLR and Quercus on JVM obviously
also JIT compile, but are not as good as HHVM.
On 10/24/2026 1:22 PM, Dan Cross wrote:
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Stuff like:
<quote>
Subclasses cannot override private methods. Subclass overrides of public >methods canrCOt even see, let alone call, the superclassrCOs private >methods. Problematic for, say, test mocks.
</quote>
In article <11bjjen$36tte$1@dont-email.me>,It tells that the author is pretty clueless about OOP.
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 1:22 PM, Dan Cross wrote:
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Stuff like:
<quote>
Subclasses cannot override private methods. Subclass overrides of public
methods canrCOt even see, let alone call, the superclassrCOs private
methods. Problematic for, say, test mocks.
</quote>
This point was listed as a weakness in the critique. It begs
the question, however, what does that sentence mean to you?
On 10/24/2026 9:14 PM, Dan Cross wrote:
In article <11bjjen$36tte$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 1:22 PM, Dan Cross wrote:
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Stuff like:
<quote>
Subclasses cannot override private methods. Subclass overrides of public >>> methods canrCOt even see, let alone call, the superclassrCOs private
methods. Problematic for, say, test mocks.
</quote>
This point was listed as a weakness in the critique. It begs
the question, however, what does that sentence mean to you?
It tells that the author is pretty clueless about OOP.
The syntax is:
mysqli_stmt_prepare(-2stmt-+, "select -2table-+ from -2table-+ where -2field-+
like ?")
and then the value is:
"%" + s + "%"
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Probably. Early development for the web was annoyingly tedious.
I remember being shocked at the things that were omitted, like
any semblence of a session model, a basic concept of identity
(beyond "HTTP Basic Authentication" headers), or any effort to
integrate with the underlying host's models at more than a
cursory level; certainly, efforts to improve the situation were
welcome along many dimensions.
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!), and again, no session
layer; all of that had to be built from scratch using cookies
or tokens in a URI or something, and any sort of integration
with existing authentication or identity sources similarly.
What about it was compelling? It was like a bunch of people
suddenly decided that building applications on top of anonymous
FTP was a good idea. I guess it had visual elements you
couldn't easily expose with VTAM over 3270s.
Dan Cross <cross@spitfire.i.gajendra.net> wrote:
Probably. Early development for the web was annoyingly tedious.
I remember being shocked at the things that were omitted, like
any semblence of a session model, a basic concept of identity
(beyond "HTTP Basic Authentication" headers), or any effort to
integrate with the underlying host's models at more than a
cursory level; certainly, efforts to improve the situation were
welcome along many dimensions.
It's not FOR that. It's for displaying hyperlinked data. It was never >intended to be stateful, it was never intended to be bidirectional and >replace forms applications. If you wanted that, a dedicated application
was how you were expected to do it. But then everybody wanted the web
to do everything all of a sudden and everything went wrong.
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!), and again, no session
layer; all of that had to be built from scratch using cookies
or tokens in a URI or something, and any sort of integration
with existing authentication or identity sources similarly.
What about it was compelling? It was like a bunch of people
suddenly decided that building applications on top of anonymous
FTP was a good idea. I guess it had visual elements you
couldn't easily expose with VTAM over 3270s.
Agreed. But the web was a wonderful thing and well-designed for
what it was designed for. You can't blame the folks who designed
it when so many people decided they wanted it to be something
totally different.
In article <11biu7b$2vhq4$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/23/2026 7:51 AM, Dan Cross wrote:
In article <20261023123938.000065e7@yahoo.com>,
Michael S <already5chosen@yahoo.com> wrote:
On Thu, 22 Oct 2026 22:43:59 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
PHP is a sorry mess, a long litany of sad design decisions.
When I first saw PHP, it looked like they were trying to copy Perl,
but not quite understanding what they were copying.
Nowadays, it looks like theyrCOve moved on to trying to copy Python. But >>>>> they still donrCOt understand what theyrCOre copying.
So why are they massively more successful than perl in their very
lucrative niche of web server-side scripting? And why at least until
recently [in this niche] they were massively more successful than
python?
My guess would be that they are doing something right.
When I first saw PHP, I assumed they were trying to provide an
alternative to ASP and CFML, where one interleaved HTML and
program snippets.
I suspect that demand created multiple similar solutions.
Probably. Early development for the web was annoyingly tedious.
I remember being shocked at the things that were omitted, like
any semblence of a session model, a basic concept of identity
(beyond "HTTP Basic Authentication" headers), or any effort to
integrate with the underlying host's models at more than a
cursory level; certainly, efforts to improve the situation were
welcome along many dimensions.
PHP 1.0 : 08-Jun-1995
ColdFusion 1.0 : 10-Jul-1995 [different sources have different dates but
they all say July]
ASP 1.0 : 10-Dec-1996
The PHP of June 1995 did not look like the PHP one sees today.
The history at https://www.php.net/manual/en/history.php.php
describes the evolution and gives an example of PHP/FI 2.0 circa
1997/1998; it is very different. That page says that PHP 3.0 is
the first version that's clearly related to the modern language.
Note that CFML typical use tags not script snippets. So in that
regard it is more like JSP with JSTL and ASP.NET web forms than
like PHP, ASP and JSP without JSTL. Or to put it differently: CFML
was 7 years ahead of the rest.
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
and again, no session
layer; all of that had to be built from scratch using cookies
or tokens in a URI or something, and any sort of integration
with existing authentication or identity sources similarly.
What about it was compelling? It was like a bunch of people
suddenly decided that building applications on top of anonymous
FTP was a good idea. I guess it had visual elements you
couldn't easily expose with VTAM over 3270s.
Of course, it's much better _now_, but lots of vestiges of those
early mistakes still linger on; with a proper session layer, for
example, CSRF would not be a thing that people still have to
worry about, and SASL never really caught on, though OIDC is...
ok, I guess?
- Dan C.
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
At the time it was built most people did not use something that could
display mathematics and fractions. For quite some time the line mode
browser (and later lynx) was the most used browser. A graphics browser
came much later and only then there grew a need for other characters
then those that could be displayed on a VT200.
On 10/24/2026 5:04 PM, Dan Cross wrote:
In article <11bj186$30n6f$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/23/2026 9:59 PM, Dan Cross wrote:
It's probably true that a language like PHP shouldn't have that
kind of thing built into it.-a But it's also true that that's a
programming error (failure to sanitize one's input).
Practically every technology provide a way to execute external
commands.
Indeed, but the danger isn't the mechanism, it is the specific
implementation.-a PHP is very often used to build applications
that are exposed to all kinds of untrusted inputs.-a Backticks in
an environment where much input is untrusted, for example, seem
unnecessarily permissive.
Almost all languages has the capability including languages
used for web.
Even if Bill write CGI script in VMS Cobol he could call LIB$SPAWN.
And unlike many other languages then it easy to block in PHP.
Just add:
disable_functions = shell_exec
to php.ini and it is gone.
term% phpeval is another function that need to be very strictly controlled.
<?php
$cmd='`pwd`';
echo $cmd;
eval("echo $cmd;");
`pwd`/home/cross
term%
Sure, its a cheat to use `eval` here, but maybe interpolation of
backticks should not be allowed anywhere except an assignment,
and perhaps PHP shouldn't have an `eval`.
Arne
In article <11bn7f8$2s502$1@dont-email.me>,
Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
Not really. Tim Brenners-Lee wrote the initial browser on the
NeXT;
At the time it was built most people did not use something that could >>display mathematics and fractions. For quite some time the line mode >>browser (and later lynx) was the most used browser. A graphics browser
came much later and only then there grew a need for other characters
then those that could be displayed on a VT200.
Is this true? `nroff` with `neqn` could produce basic, ASCII
art equations that displayed decently well on terminals back in
the 1980s. Certainly lots of folks had bitmapped graphics
displays by the early 90s.
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <11bn7f8$2s502$1@dont-email.me>,
Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
Not really. Tim Brenners-Lee wrote the initial browser on the
NeXT;
At the time it was built most people did not use something that could >>>display mathematics and fractions. For quite some time the line mode >>>browser (and later lynx) was the most used browser. A graphics browser >>>came much later and only then there grew a need for other characters
then those that could be displayed on a VT200.
Is this true? `nroff` with `neqn` could produce basic, ASCII
art equations that displayed decently well on terminals back in
the 1980s. Certainly lots of folks had bitmapped graphics
displays by the early 90s.
I've a 9-track tape full of posters suitable for printing
on standard 132-column printers with greenbar (or better
white) fanfold paper. Dates to the late 1970s.
Including a wall-sized moon and a picture of a 727
flying under the golden gate bridge
In article <DRMDS.14957$V9C6.3059@fx02.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <11bn7f8$2s502$1@dont-email.me>,
Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
Not really. Tim Brenners-Lee wrote the initial browser on the
NeXT;
At the time it was built most people did not use something that could >>>>display mathematics and fractions. For quite some time the line mode >>>>browser (and later lynx) was the most used browser. A graphics browser >>>>came much later and only then there grew a need for other characters >>>>then those that could be displayed on a VT200.
Is this true? `nroff` with `neqn` could produce basic, ASCII
art equations that displayed decently well on terminals back in
the 1980s. Certainly lots of folks had bitmapped graphics
displays by the early 90s.
I've a 9-track tape full of posters suitable for printing
on standard 132-column printers with greenbar (or better
white) fanfold paper. Dates to the late 1970s.
Including a wall-sized moon and a picture of a 727
flying under the golden gate bridge
Wow, I wouldn't mind seeing either of those! They sound cool.
In article <11bn7f8$2s502$1@dont-email.me>,
Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
Not really. Tim Brenners-Lee wrote the initial browser on the
NeXT;
The start of WWW was very much text. Lynx browser and various GopherAt the time it was built most people did not use something that could
display mathematics and fractions. For quite some time the line mode
browser (and later lynx) was the most used browser. A graphics browser
came much later and only then there grew a need for other characters
then those that could be displayed on a VT200.
Is this true? `nroff` with `neqn` could produce basic, ASCII
art equations that displayed decently well on terminals back in
the 1980s. Certainly lots of folks had bitmapped graphics
displays by the early 90s.
The start of WWW was very much text. Lynx browser and various Gopher
clients.
NeXT was not widely used.
But the GUI browsers did hid the mass market pretty soon.
Mosaic 1993
NetScape 1994
On 10/26/2026 12:48 PM, Dan Cross wrote:
In article <11bn7f8$2s502$1@dont-email.me>,
Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 24.okt.2026 om 22:11 schreef Dan Cross:
[snip]
Ok. I just thought it was very strange that so many people
embraced the web so enthusiastically; the protocol was awful,
the markup language underpowered (it couldn't even represent
basic mathematics, like fractions!),
That is out of the context of that time.
Not really. Tim Brenners-Lee wrote the initial browser on the
NeXT;
Tim Berners-Lee
At the time it was built most people did not use something that could
display mathematics and fractions. For quite some time the line mode
browser (and later lynx) was the most used browser. A graphics browser
came much later and only then there grew a need for other characters
then those that could be displayed on a VT200.
Is this true? `nroff` with `neqn` could produce basic, ASCII
art equations that displayed decently well on terminals back in
the 1980s. Certainly lots of folks had bitmapped graphics
displays by the early 90s.
The start of WWW was very much text. Lynx browser and various Gopher
clients.
NeXT was not widely used.
But the GUI browsers did hid the mass market pretty soon.
Mosaic 1993
NetScape 1994
Internet Explorer 1995
And math was actually proposed back then.
The HTML 3.0 proposal (1995) had math.
But it never became standard.
For two reasons:
* too big a change for browsers to implement (I have no
idea whether text based browsers played a role in that
discussion)
* no interest from NetScape and Microsoft as they were
looking for more "flashy" things as part of their
competition for the browser market - math support
is not important in that regard
Next standard became HTML 3.2 in 1997 without math.
Math was kicked off to MathML and was first included
in HTML almost two decades later.
The start of WWW was very much text. Lynx browser and various Gopher
clients.
NeXT was not widely used.
But the GUI browsers did hid the mass market pretty soon.
Mosaic 1993
NetScape 1994
Internet Explorer 1995
cross@spitfire.i.gajendra.net (Dan Cross) writes:
In article <DRMDS.14957$V9C6.3059@fx02.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
[snip]]
Including a wall-sized moon and a picture of a 727
flying under the golden gate bridge
Wow, I wouldn't mind seeing either of those! They sound cool.
Al copied the tape to cdrom for me many years ago now. He should
have it up on bitsavers somewhere.
In article <11bjlgb$37fah$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 9:14 PM, Dan Cross wrote:
In article <11bjjen$36tte$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 1:22 PM, Dan Cross wrote:
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Stuff like:
<quote>
Subclasses cannot override private methods. Subclass overrides of public >>>> methods canrCOt even see, let alone call, the superclassrCOs private
methods. Problematic for, say, test mocks.
</quote>
This point was listed as a weakness in the critique. It begs
the question, however, what does that sentence mean to you?
It tells that the author is pretty clueless about OOP.
Are you sure? Is there a single, universal, definition of the
semantics of `private` in Object-Oriented languages? (Hint:
have you ever used Ruby? Smalltalk?)
Can you think of another explanation they may be driving at?
For instance, mabye they are questioning why a dynamic language
like PHP has a definition of `private` that is as rigid as
C++'s, while not also providing a `friend`-like abstraction.
On Sat, 24 Oct 2026 21:02:37 -0400, Arne Vajhoj wrote:
The syntax is:
mysqli_stmt_prepare(2stmt+, "select 2table+ from 2table+ where 2field+
like ?")
and then the value is:
"%" + s + "%"
Shall I point out what is wrong with that?
On Sat, 24 Oct 2026 11:59:30 -0400, Arne Vajhoj wrote:
Always === is a good workaround.
A workaround is still a workaround. The weak typing that led to its
necessity is not ?good?.
I assume you've seen this? I think I may have posted it a
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
On Sat, 24 Oct 2026 20:45:24 -0400, Arne Vajhoj wrote:
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Discussing the PHP bug on another forum, another commenter offered
this little gem:
$a = INF;
$b = [];
$c = (object)[];
var_dump($a < $b); // true, as INF is less than an array
var_dump($b < $c); // true, as an array is less than an object
var_dump($c < $a); // true, as an object is less than INF
Is there such a thing as a ?rock-paper-scissors? sorting algorithm?
Seems like PHP has it ...
On Sat, 24 Oct 2026 20:02:57 -0400, Arne Vajh|+j wrote:
PHP applications often do web sockets.
Does not seem to be a problem in the real world.
They canrCOt.
WebSocket connections require an ongoing running task toWeb is mostly HTTP(S) request and response - that does not
manage the server end of the connection, which doesnrCOt fit into the
PHP request/response model.
On 2026-10-24, Lawrence D Oliveiro <ldo@nz.invalid> wrote:
On Sat, 24 Oct 2026 20:45:24 -0400, Arne Vajhoj wrote:
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Discussing the PHP bug on another forum, another commenter offered
this little gem:
$a = INF;
$b = [];
$c = (object)[];
var_dump($a < $b); // true, as INF is less than an array
var_dump($b < $c); // true, as an array is less than an object
var_dump($c < $a); // true, as an object is less than INF
Is there such a thing as a ?rock-paper-scissors? sorting algorithm?
Seems like PHP has it ...
Now do Javascript...
Simon.
PS: IOW, why are the most popular web languages (both client and server-side) >so bloody insanely bad ? :-(
The two most common approaches for web sockets in PHP are:
* any web server with PHP using any execution model serving
the pages combined with a PHP CLI process serving web sockets
* one of the modern PHP application servers (RoadRunner,
FrankenPHP etc.)
On 2026-10-24, Dan Cross <cross@spitfire.i.gajendra.net> wrote:
I assume you've seen this? I think I may have posted it a
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I had forgotten about this and it sums up things better than I can.
BTW, I have yet to see someone propose a Rust-style scripting
language as a replacement for PHP. :-)
On a more serious note, I wish Python had taken hold instead of PHP
in the web server world. I get on far better with Python than PHP and
Python is a much more general purpose language that is the scripting
language in all kinds of applications.
Oh, and about the bit in the above URL about calling a PHP function
and passing an array as its arguments, have a look at the splat operator >introduced in current PHP versions to unpack an array as an argument list.
Had cause to use it recently (I sometimes have to write PHP code to
interface with things) and it appeared to work for me. It may do what
you need in some circumstances instead of call_user_func_array().
On a more serious note, I wish Python had taken hold instead of PHP
in the web server world. I get on far better with Python than PHP and
Python is a much more general purpose language that is the scripting
language in all kinds of applications.
On Tue, 27 Oct 2026 17:19:00 -0400, Arne Vajh|+j wrote:
The two most common approaches for web sockets in PHP are:
* any web server with PHP using any execution model serving
the pages combined with a PHP CLI process serving web sockets
ThatrCOs a clunky way, running two separate components that have to
figure out some way of communicating between them. Particularly since
only one side can respond to internal events, the other canrCOt.
* one of the modern PHP application servers (RoadRunner,
FrankenPHP etc.)
But thatrCOs not compatible all this existing code written for mod_php/PHP-FPM!
Can I use them with WordPress? No.FrankenPHP : yes - see https://frankenphp.dev/docs/wordpress/
In article <11bji28$36hh1$1@dont-email.me>,I can not follow.
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 5:04 PM, Dan Cross wrote:
In article <11bj186$30n6f$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/23/2026 9:59 PM, Dan Cross wrote:
It's probably true that a language like PHP shouldn't have that
kind of thing built into it. But it's also true that that's a
programming error (failure to sanitize one's input).
Practically every technology provide a way to execute external
commands.
Indeed, but the danger isn't the mechanism, it is the specific
implementation. PHP is very often used to build applications
that are exposed to all kinds of untrusted inputs. Backticks in
an environment where much input is untrusted, for example, seem
unnecessarily permissive.
Almost all languages has the capability including languages
used for web.
...and?
Even if Bill write CGI script in VMS Cobol he could call LIB$SPAWN.
...and?
And unlike many other languages then it easy to block in PHP.
Just add:
disable_functions = shell_exec
to php.ini and it is gone.
This misses the point. A) the person writing the program has to
be the one configuring `php.ini`. B) you are comparing
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
On 10/27/2026 6:49 PM, Lawrence DrCOOliveiro wrote:
On Tue, 27 Oct 2026 17:19:00 -0400, Arne Vajh|+j wrote:
The two most common approaches for web sockets in PHP are:
* any web server with PHP using any execution model serving
the pages combined with a PHP CLI process serving web sockets
ThatrCOs a clunky way, running two separate components that have to
figure out some way of communicating between them. Particularly
since only one side can respond to internal events, the other
canrCOt.
Multiple processes are quite common for web solutions.
* one of the modern PHP application servers (RoadRunner,
FrankenPHP etc.)
But thatrCOs not compatible all this existing code written for
mod_php/PHP-FPM!
You should not write PHP code for mod_php or PHP-FPM.
You should write PHP code for PHP.
Your PHP code should run fine with all execution models
(mod_php, PHP-FPM, RoadRunner and FreankenPHP).
Can I use them with WordPress? No.FrankenPHP : yes - see https://frankenphp.dev/docs/wordpress/
RoadRunner : no - there is some problem with WP and some
other CMS - you would need to pick a CMS that work in that
context (all Laravel and Symfony based CMS should work)
The biggest difference in security is that one can disable
shell_exec (and exec and passthru and proc_* and system) and still
run PHP while it is a bit hard to disable LIB$SPAWN (and
LIB$DO_COMMAND and SYS$CREPRC) without disabling CGI.
There are plenty of web frameworks in Python.
On 10/27/2026 3:33 PM, Simon Clubley wrote:
On a more serious note, I wish Python had taken holdinstead of PHP
in the web server world. I get on far better with Pythonthan PHP and
Python is a much more general purpose language that isthe scripting
language in all kinds of applications.
There are plenty of web frameworks in Python.
If you like "HTML 5" (which you probably don't because that
means JS/TS client side) then maybe Flask or FastAPI.
And on the content side, existing services like Compuserve, Prodigy,
AOL etc felt that the open Internet could never offer the quality of
content available (at a price) on their proprietary platforms. In the
end, connectivity won out over content, and they had to abandon their proprietary connections and embrace the Internet to survive.
On 10/24/2026 8:45 PM, Dan Cross wrote:
In article <11bji28$36hh1$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
[snip]
Almost all languages has the capability including languages
used for web.
...and?
Even if Bill write CGI script in VMS Cobol he could call LIB$SPAWN.
...and?
And unlike many other languages then it easy to block in PHP.
Just add:
disable_functions = shell_exec
to php.ini and it is gone.
This misses the point. A) the person writing the program has to
be the one configuring `php.ini`.
B) you are comparingI can not follow.
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
Let me show some code. I will substitute Cobol with Fortran
[snip]
But I don't see any of the differences matter from a
security perspective.
On Tue, 27 Oct 2026 20:33:13 -0400, Arne Vajh|+j wrote:
The biggest difference in security is that one can disable shell_exec (and >> exec and passthru and proc_* and system) and still run PHP while it is a bit >> hard to disable LIB$SPAWN (and LIB$DO_COMMAND and SYS$CREPRC) without
disabling CGI.
Another issue is that VMS suffers from the same fundamental limitation as Windows: why the call is named "shell_exec" in the first place -- because it is assumed to be always be going through a shell.
On Unix-type systems, it is common for one program to directly spawn another without going through a shell. This avoids, at one stroke, all the potential problems with having to escape characters with special meanings to the
shell. For example, dollar signs and spaces in file names, special characters indicating pipes, redirections etc. This makes the spawning of external commands much safer.
On Tue, 27 Oct 2026 20:33:13 -0400, Arne Vajh|+j wrote:
The biggest difference in security is that one can disable
shell_exec (and exec and passthru and proc_* and system) and still
run PHP while it is a bit hard to disable LIB$SPAWN (and
LIB$DO_COMMAND and SYS$CREPRC) without disabling CGI.
Another issue is that VMS suffers from the same fundamental limitation
as Windows: why the call is named rCLshell_execrCY in the first place -- because it is assumed to be always be going through a shell.
On Unix-type systems, it is common for one program to directly spawn
another without going through a shell. This avoids, at one stroke, all
the potential problems with having to escape characters with special
meanings to the shell. For example, dollar signs and spaces in file
names, special characters indicating pipes, redirections etc. This
makes the spawning of external commands much safer.
On 10/28/2026 12:47 AM, Lawrence DrCOOliveiro wrote:
Another issue is that VMS suffers from the same fundamental
limitation as Windows: why the call is named rCLshell_execrCY in the
first place -- because it is assumed to be always be going through
a shell.
On Unix-type systems, it is common for one program to directly
spawn another without going through a shell. This avoids, at one
stroke, all the potential problems with having to escape characters
with special meanings to the shell. For example, dollar signs and
spaces in file names, special characters indicating pipes,
redirections etc. This makes the spawning of external commands much
safer.
Hmmm.
First then the shell question is not really an issue on VMS. On VMS
starting a program via shell does not create two processes - it only
creates one process with DCL in P1 and the program in P0/P2.
Second then on VMS it is possible to create a process with DCL mapped
or a process without DCL mapped - your choice.
call lib$spawn('run p2')
On 10/28/2026 12:47 AM, Lawrence DrCOOliveiro wrote:
Another issue is that VMS suffers from the same fundamental
limitation as Windows: why the call is named rCLshell_execrCY in the
first place -- because it is assumed to be always be going through
a shell.
On Unix-type systems, it is common for one program to directly
spawn another without going through a shell. This avoids, at one
stroke, all the potential problems with having to escape characters
with special meanings to the shell. For example, dollar signs and
spaces in file names, special characters indicating pipes,
redirections etc. This makes the spawning of external commands much
safer.
Hmmm.
First then the shell question is not really an issue on VMS. On VMS
starting a program via shell does not create two processes - it only
creates one process with DCL in P1 and the program in P0/P2.
Second then on VMS it is possible to create a process with DCL mapped
or a process without DCL mapped - your choice.
In article <11brcg1$1vuaq$1@dont-email.me>,True. But not so relevant.
Arne Vajh|+j <arne@vajhoej.dk> wrote:
If you like "HTML 5" (which you probably don't because that
means JS/TS client side) then maybe Flask or FastAPI.
Huh? No it doesn't. You can use HTML 5 without any client side
scripting at all.
In article <11bji28$36hh1$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
And unlike many other languages then it easy to block in PHP.
Just add:
disable_functions = shell_exec
to php.ini and it is gone.
This misses the point. A) the person writing the program has to
be the one configuring `php.ini`.
In article <11brfro$20u59$1@dont-email.me>,I showed that native languages had the same
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 8:45 PM, Dan Cross wrote:
B) you are comparingI can not follow.
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
Let me show some code. I will substitute Cobol with Fortran
No. You posted three code snippets that all do approximately
the same thing, but at the same time, failed to address the
substance of what i raised above.
[snip]
But I don't see any of the differences matter from a
security perspective.
That was the point.
On Wed, 28 Oct 2026 20:44:54 -0400, Arne Vajh|+j wrote:
call lib$spawn('run p2')
What if a command argument has spaces in it?
On Wed, 28 Oct 2026 20:44:54 -0400, Arne Vajh|+j wrote:
On 10/28/2026 12:47 AM, Lawrence DrCOOliveiro wrote:
On Unix-type systems, it is common for one program to directly
spawn another without going through a shell. This avoids, at one
stroke, all the potential problems with having to escape characters
with special meanings to the shell. For example, dollar signs and
spaces in file names, special characters indicating pipes,
redirections etc. This makes the spawning of external commands much
safer.
Hmmm.
First then the shell question is not really an issue on VMS. On VMS
starting a program via shell does not create two processes - it only
creates one process with DCL in P1 and the program in P0/P2.
ThatrCOs not the issue, though. The issue is how you pass command-line arguments to the spawned program.
Second then on VMS it is possible to create a process with DCL mapped
or a process without DCL mapped - your choice.
If you want to pass a command line, you need to have a command-line interpreter -- no choice.
So my original comment does need a correction: VMS doesnrCOt quite
suffer from the rCLsame fundamental limitationrCY as Windows: it suffers
from a worse one.
Without Wordpress, you have lost perhaps 90% of the reason for writing
PHP code in the first place.
On 2026-10-24, Lawrence D|+Oliveiro <ldo@nz.invalid> wrote:I think the natural association is that === means "more equal"
On Sat, 24 Oct 2026 11:59:30 -0400, Arne Vajh|+j wrote:
Always === is a good workaround.
A workaround is still a workaround. The weak typing that led to its
necessity is not ?good?.
I disagree with you on many things, but agree with you on that one.
You should get strict equality by default with "==" and have to use
"===" to get loose equality.
On 10/28/2026 4:52 AM, Dan Cross wrote:
In article <11brcg1$1vuaq$1@dont-email.me>,True. But not so relevant.
Arne Vajh|+j <arne@vajhoej.dk> wrote:
If you like "HTML 5" (which you probably don't because that
means JS/TS client side) then maybe Flask or FastAPI.
Huh? No it doesn't. You can use HTML 5 without any client side
scripting at all.
Despite the name then a HTML 5 web app is not a web app
generating HTML 5 but a web app running client side with
JavaScript code making web service calls to get data and
managing the rendering.
[snip]
A way more correct term is Client Side Rendering. But it
is not as widely used.
We are stuck with the "HTML 5" term. I like to put it
in quotation marks to indicate that it is not what it
says it is.
On 10/28/2026 1:22 PM, Dan Cross wrote:
In article <11brfro$20u59$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 8:45 PM, Dan Cross wrote:
B) you are comparingI can not follow.
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
Let me show some code. I will substitute Cobol with Fortran
No. You posted three code snippets that all do approximately
the same thing, but at the same time, failed to address the
substance of what i raised above.
[snip]
But I don't see any of the differences matter from a
security perspective.
That was the point.
I showed that native languages had the same
issue as PHP.
And unlike with PHP there is no easy way to close the
problem.
And what does that mean?
It means that from a shell executing perspective then
rational people should recommend using PHP over
native languages like Cobol and Fortran.
Obviously there can be many other security related
reasons to not use PHP, but shell executing is not
one of them.
They should disable the dangerous PHP functions.
On 10/28/2026 12:44 AM, Lawrence DrCOOliveiro wrote:
Without Wordpress, you have lost perhaps 90% of the reason for
writing PHP code in the first place.
????
Most people use WP to avoid having to write PHP (or any other
programming language).
In article <11bjlgb$37fah$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 9:14 PM, Dan Cross wrote:
In article <11bjjen$36tte$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 1:22 PM, Dan Cross wrote:
I assume you've seen this? I think I may have posted it aYou have posted it before.
couple of days ago.
https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/
I am not sure whether to laugh or cry.
Stuff like:
<quote>
Subclasses cannot override private methods. Subclass overrides of public >>>> methods canrCOt even see, let alone call, the superclassrCOs private
methods. Problematic for, say, test mocks.
</quote>
This point was listed as a weakness in the critique. It begs
the question, however, what does that sentence mean to you?
It tells that the author is pretty clueless about OOP.
Are you sure? Is there a single, universal, definition of the
semantics of `private` in Object-Oriented languages?
(Hint:
have you ever used Ruby? Smalltalk?)
Can you think of another explanation they may be driving at?
For instance, mabye they are questioning why a dynamic language
like PHP has a definition of `private` that is as rigid as
C++'s, while not also providing a `friend`-like abstraction.
Having a global config file to control language features is a stupid
idea.
On Fri, 30 Oct 2026 14:54:08 -0400, Arne Vajh|+j wrote:
On 10/28/2026 12:44 AM, Lawrence DrCOOliveiro wrote:
Without Wordpress, you have lost perhaps 90% of the reason for
writing PHP code in the first place.
????
Most people use WP to avoid having to write PHP (or any other
programming language).
You donrCOt know about the whole Wordpress themes/plugins ecosystem?
term% ruby
class A
def foo
bar
end
private
def bar
puts "Hello from A's bar"
end
end
class B < A
private
def bar
puts "Hello from B's bar"
end
end
a = A.new
a.foo
b = B.new
b.foo
Hello from A's bar
Hello from B's bar
In *this* language, `private` doesn't mean what it means in C++.
In article <11c2mfu$fsse$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/28/2026 1:22 PM, Dan Cross wrote:
In article <11brfro$20u59$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 8:45 PM, Dan Cross wrote:
B) you are comparingI can not follow.
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
Let me show some code. I will substitute Cobol with Fortran
No. You posted three code snippets that all do approximately
the same thing, but at the same time, failed to address the
substance of what i raised above.
[snip]
But I don't see any of the differences matter from a
security perspective.
That was the point.
I showed that native languages had the same
issue as PHP.
No, you really did not. You merely showed that other languages
can spawn programs using `LIB$SPAWN` or similar mechanisms.
What you missed is that it is the unique combination of
anti-patterns manifest in PHP that make it dangerouus in this
regard.
Consider this analogy: `strcpy()` is dangerous because you
cannot tell it how big the destination buffer is. `strlcpy()`
is much safer because you _do_ tell it the size of the
destination buffer, it promises to NUL-terminate the destination
(as long as size>0), _and_ it tells how much space the source
required, so that you can detect truncation. That doesn't mean
that it is perfectly safe, because you can still give it a bad
destination length; you _can_ call it with `SIZE_MAX`, but most
programmers do not.
And unlike with PHP there is no easy way to close the
problem.
I doubt that disabling shell actually prevents you from calling
`LIB$SPAWN` via other means.
On Fri, 30 Oct 2026 14:04:22 -0400, Arne Vajh|+j wrote:As with anything else then it would need to be looked at.
They should disable the dangerous PHP functions.
What if that breaks a particular PHP application that somebody needs
to run?
If you want to go the simpler route, then I will suggest an
unusual tech stack.
JSP with JSTL as view. That mean all tags no script snippets
in view - tags is also some sort of code but very structured.
Groovy grovelets as backend code. It is just another script
language, but:
* most of the easiness you expect from a script language
* no funkyness with ==
* optional typing but if a type is specified then it is enforced - it
-a is not just a hint
But having a central config file to control the security of aNote that besides PHP there is one other web technology
server is a smart idea.
And this is a server config.
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
Having a global config file to control language features is a
stupid idea.
But having a central config file to control the security of a server
is a smart idea.
Note that besides PHP there is one other web technology available on
VMS that can block shell access.
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
As with anything else then it would need to be looked at.
On Fri, 30 Oct 2026 14:04:22 -0400, Arne Vajh|+j wrote:
They should disable the dangerous PHP functions.
What if that breaks a particular PHP application that somebody
needs to run?
* Python without type hint, Python with type hint, PHP and Groovy
without type
happily allows variables changing type with assignment [BAD]
Let us look at function overload.
$ type fol.py
def f(v: int):
print(f"int : {v}")
def f(v: str):
print(f"str : {v}")
And I know you can code in Groovy. :-)
On Sat, 14 Nov 2026 13:23:20 -0500, Arne Vajh|+j wrote:
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
On Fri, 30 Oct 2026 14:04:22 -0400, Arne Vajh|+j wrote:As with anything else then it would need to be looked at.
They should disable the dangerous PHP functions.
What if that breaks a particular PHP application that somebody
needs to run?
The whole concept of a global mechanism for configuring language
features is wrong.
On Sat, 14 Nov 2026 14:08:58 -0500, Arne Vajh|+j wrote:
Note that besides PHP there is one other web technology available on
VMS that can block shell access.
On Linux, you rely on more wide-ranging access controls, like container namespaces. Those controls work across all languages, all runtimes, all libraries, all everything, because they are enforced by the kernel.
*That* is how to do security. Not by relying on poorly-designed
mechanisms specific to one poorly-designed language.
On 11/14/2026 5:19 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 14:08:58 -0500, Arne Vajh|+j wrote:
Note that besides PHP there is one other web technology available
on VMS that can block shell access.
On Linux, you rely on more wide-ranging access controls, like
container namespaces. Those controls work across all languages, all
runtimes, all libraries, all everything, because they are enforced
by the kernel.
*That* is how to do security. Not by relying on poorly-designed
mechanisms specific to one poorly-designed language.
It is not an alternative to hardening application and server. It is
an addition.
On Sat, 14 Nov 2026 13:22:17 -0500, Arne Vajh|+j wrote:
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
Having a global config file to control language features is a
stupid idea.
But having a central config file to control the security of a server
is a smart idea.
But php.ini doesnrCOt do that. It only covers PHP.
On 11/14/2026 5:20 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 13:23:20 -0500, Arne Vajh|+j wrote:
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
As with anything else then it would need to be looked at.
On Fri, 30 Oct 2026 14:04:22 -0400, Arne Vajh|+j wrote:
They should disable the dangerous PHP functions.
What if that breaks a particular PHP application that somebody
needs to run?
The whole concept of a global mechanism for configuring language
features is wrong.
But this is not.
This is a server or application config (depending on execution
model).
On 11/14/2026 5:17 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 13:22:17 -0500, Arne Vajh|+j wrote:
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
Having a global config file to control language features is a
stupid idea.
But having a central config file to control the security of a
server is a smart idea.
But php.ini doesnrCOt do that. It only covers PHP.
True. But point is that it is central - not that it is one file.
If you have an Apache and are using mod_php to run PHP, then you
have a httpd.conf, various included .conf files (like one for SSL
and one for PHP) and you have a php.ini.
They get created by admin/operations. They get audited by internal
and external IS.
On Sat, 14 Nov 2026 17:37:24 -0500, Arne Vajh|+j wrote:
On 11/14/2026 5:19 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 14:08:58 -0500, Arne Vajh|+j wrote:
Note that besides PHP there is one other web technology available
on VMS that can block shell access.
On Linux, you rely on more wide-ranging access controls, like
container namespaces. Those controls work across all languages, all
runtimes, all libraries, all everything, because they are enforced
by the kernel.
*That* is how to do security. Not by relying on poorly-designed
mechanisms specific to one poorly-designed language.
It is not an alternative to hardening application and server. It is
an addition.
You were talking about blocking shell access. You can set up a Linux container that only runs the one app as pid 1, with no rCLshellrCY
anywhere in the visible filesystem to access.
*That* is how to rCLblock shell accessrCY.
On 11/14/2026 5:40 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 17:37:24 -0500, Arne Vajh|+j wrote:
On 11/14/2026 5:19 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 14:08:58 -0500, Arne Vajh|+j wrote:
Note that besides PHP there is one other web technology
available on VMS that can block shell access.
On Linux, you rely on more wide-ranging access controls, like
container namespaces. Those controls work across all languages,
all runtimes, all libraries, all everything, because they are
enforced by the kernel.
*That* is how to do security. Not by relying on poorly-designed
mechanisms specific to one poorly-designed language.
It is not an alternative to hardening application and server. It
is an addition.
You were talking about blocking shell access. You can set up a
Linux container that only runs the one app as pid 1, with no
rCLshellrCY anywhere in the visible filesystem to access.
*That* is how to rCLblock shell accessrCY.
No shell obvious prevent shell access.
But you should talk to the guy that like to post to comp.os.vms
about how Linux allows for starting a process without a shell
avoiding the need for escaping.
Containers are a great technology, but it is not the right tool to
prevent web applications from executing commands.
On Sat, 14 Nov 2026 17:41:59 -0500, Arne Vajh|+j wrote:
On 11/14/2026 5:17 PM, Lawrence DrCOOliveiro wrote:
On Sat, 14 Nov 2026 13:22:17 -0500, Arne Vajh|+j wrote:
On 10/30/2026 7:06 PM, Lawrence DrCOOliveiro wrote:
Having a global config file to control language features is a
stupid idea.
But having a central config file to control the security of a
server is a smart idea.
But php.ini doesnrCOt do that. It only covers PHP.
True. But point is that it is central - not that it is one file.
Central meaning it affects *all* apps running under that PHP
installation.
If you have an Apache and are using mod_php to run PHP, then you
have a httpd.conf, various included .conf files (like one for SSL
and one for PHP) and you have a php.ini.
If I were running a Python app, I would still have all the Apache
config, no Python-specific Apache module (thank goodness), and no
python.ini.
What I might also have is separate systemd .service files, one for
running each application,
On 11/14/2026 5:48 PM, Lawrence DrCOOliveiro wrote:
What I might also have is separate systemd .service files, one for
running each application,
Similar to what the modern PHP servers does.
It wastes memory, but provides flexibility.
On Sat, 14 Nov 2026 19:42:33 -0500, Arne Vajh|+j wrote:
On 11/14/2026 5:48 PM, Lawrence DrCOOliveiro wrote:
What I might also have is separate systemd .service files, one for
running each application,
Similar to what the modern PHP servers does.
It wastes memory, but provides flexibility.
ItrCOs the only rational way to do it.
PHP servers like PHP-FPM, of course, just transplant the original
mod_php environment into an isolated process, unchanged. And they use
creaky old protocols like FastCGI to communicate back to the web
server. (Heard of anything else that uses FastCGI? I havenrCOt.)
The approach used by other languages, like NodeJS and Python, is to
have your app run its own mini-HTTP server, which is rCLreverserCY proxied through a rCLrealrCY web server (Apache, Nginx etc) to the outside world.
The latter takes care of the tricky stuff like SSL/TLS and virtual
hosting, and of course helping to keep the bad guys out, while your
app gets its own event loop, its own ability to run background tasks according to its own triggers, and the ability to handle asynchronous requests and maintain long-running connections like WebSockets.
There is also a similar move in the PHP world. From Apache+mod_php, Apache+FPM, niginx+FPM etc. to FrankenPHP, RoadRunner etc..
And async background tasks would typical be handed off to something
else via a message queue.
On 10/26/2026 9:21 PM, Dan Cross wrote:
term% ruby
class A
def foo
bar
end
private
def bar
puts "Hello from A's bar"
end
end
class B < A
private
def bar
puts "Hello from B's bar"
end
end
a = A.new
a.foo
b = B.new
b.foo
Hello from A's bar
Hello from B's bar
In *this* language, `private` doesn't mean what it means in C++.
In Ruby it means object private instead of class private. And as
demonstrated in my other post then it is a OO encapsulation
disaster.
But the second example quoted here is actually not different from C++. >Because C++ interprets visibility as just that and does not
include overrideability.
On 10/30/2026 5:56 PM, Dan Cross wrote:
In article <11c2mfu$fsse$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/28/2026 1:22 PM, Dan Cross wrote:
In article <11brfro$20u59$1@dont-email.me>,
Arne Vajh|+j <arne@vajhoej.dk> wrote:
On 10/24/2026 8:45 PM, Dan Cross wrote:
B) you are comparingI can not follow.
interfaces that are designed for _explicit_ use in controlled
ways with one designed to easily interpolate values that are
ambient *in the lexical context of the invoking code*. One is
significantly _easier_ to misuse than the other. Because that
language is also designed to process inherently untrusted data,
it must be used with significant care; yet it is positioned as
the easy-to-use beginners language. That's a dangerous mix.
Let me show some code. I will substitute Cobol with Fortran
No. You posted three code snippets that all do approximately
the same thing, but at the same time, failed to address the
substance of what i raised above.
[snip]
But I don't see any of the differences matter from a
security perspective.
That was the point.
I showed that native languages had the same
issue as PHP.
No, you really did not. You merely showed that other languages
can spawn programs using `LIB$SPAWN` or similar mechanisms.
That *is* the same issue as shell_exec in PHP.
What you missed is that it is the unique combination of
anti-patterns manifest in PHP that make it dangerouus in this
regard.
The ability to execute shell commands is the ability
to execute shell commands. No more no less.
Consider this analogy: `strcpy()` is dangerous because you
cannot tell it how big the destination buffer is. `strlcpy()`
is much safer because you _do_ tell it the size of the
destination buffer, it promises to NUL-terminate the destination
(as long as size>0), _and_ it tells how much space the source
required, so that you can detect truncation. That doesn't mean
that it is perfectly safe, because you can still give it a bad
destination length; you _can_ call it with `SIZE_MAX`, but most
programmers do not.
The analogy is whether C is less safe or as safe/unsafe
as another language XYZ that has a let us say cpystr function
with the same problem.
And the answer is that C is as safe/unsafe as XYZ (in
this regard).
And unlike with PHP there is no easy way to close the
problem.
I doubt that disabling shell actually prevents you from calling
`LIB$SPAWN` via other means.
There is a list of functions able to spawn shell commands. I
even think I listed them in another post. Disable them all
and no spawn.
On Sat, 14 Nov 2026 17:58:38 -0500, Arne Vajhoj wrote:
Containers are a great technology, but it is not the right tool to
prevent web applications from executing commands.
If the commands are not visible in the filesystem, there is no way to
start them.
Your compromised application writes out a basic executable and then
executes it.
SELinux and other MAC technologies are probably a better way for
_helping_ to keep a compromised application contained.
Nothing to stop you using them alongside other tools and technologies however for a layered approach. Don't forget that security is a process
and a mindset, not a magic bullet.
Simon.
And to be very blunt, there is ~no documentation for writing secure
apps on OpenVMS.
On Mon, 16 Nov 2026 23:26:18 -0500, Stephen Hoffman wrote:
And to be very blunt, there is ~no documentation for writing secure
apps on OpenVMS.
There seems to be this myth that VMS was somehow immune to the
security vulnerabilities that plague other platforms on the Internet.
On 2026-11-16 20:25:51 +0000, Simon Clubley said:
Your compromised application writes out a basic executable and then
executes it.
Yep.
Variously without even writing files: https://en.wikipedia.org/wiki/ Fileless_malware
SELinux and other MAC technologies are probably a better way for
_helping_ to keep a compromised application contained.
Yep.
Or as an internediate and somewhat smaller implememation effort, pledge: https://myunix.org/bsd/openbsd-pledge-unveil/
Nothing to stop you using them alongside other tools and technologies
however for a layered approach. Don't forget that security is a
process and a mindset, not a magic bullet.
Yep
Software is "done" just as lawns are "mowed", of course.
And to be very blunt, there is ~no documentation for writing secure apps
on OpenVMS.
The system security manual is badly dated and woefully incomplete, the source code examples are problematic at best, the ACME API eschews the
easy stuff, the TLS APIs are a moving target, CDSA is decades
deprecated, etc.
Simon.
Yep.
What somebody with a pile of spare tokens and an inclination to reverse- engineer OpenVMS might eventually find?
Fun Times.
On 2026-11-16, Lawrence D|+Oliveiro <ldo@nz.invalid> wrote:
On Mon, 16 Nov 2026 23:26:18 -0500, Stephen Hoffman wrote:
And to be very blunt, there is ~no documentation for writing secure
apps on OpenVMS.
There seems to be this myth that VMS was somehow immune to the
security vulnerabilities that plague other platforms on the Internet.
And when you prove that it's not immune some people get very annoyed
with you and go into denial.
On 11/17/26 08:51, Simon Clubley wrote:
On 2026-11-16, Lawrence D Oliveiro <ldo@nz.invalid> wrote:
On Mon, 16 Nov 2026 23:26:18 -0500, Stephen Hoffman wrote:
And to be very blunt, there is ~no documentation for writing secure
apps on OpenVMS.
There seems to be this myth that VMS was somehow immune to the
security vulnerabilities that plague other platforms on the Internet.
And when you prove that it's not immune some people get very annoyed
with you and go into denial.
DISA was well aware and actually published security guides for VMS.
At least until DOD lost all interest in VMS. I was there in 2009
and it was somewhere before then.
On 2026-11-17, Bill Gunshannon <bill.gunshannon@gmail.com> wrote:
On 11/17/26 08:51, Simon Clubley wrote:
On 2026-11-16, Lawrence D|+Oliveiro <ldo@nz.invalid> wrote:
On Mon, 16 Nov 2026 23:26:18 -0500, Stephen Hoffman wrote:
And to be very blunt, there is ~no documentation for writing secure
apps on OpenVMS.
There seems to be this myth that VMS was somehow immune to the
security vulnerabilities that plague other platforms on the Internet.
And when you prove that it's not immune some people get very annoyed
with you and go into denial.
DISA was well aware and actually published security guides for VMS.
At least until DOD lost all interest in VMS. I was there in 2009
and it was somewhere before then.
None of that stopped the poor DEFCON 16 people from being shouted at
by some people in denial and people like me having to explain certain
basic things to those same people in denial around here.
Simon.
PS: Those guides also didn't help when it was my turn to be the target
of people in denial a few years later. :-)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (1 / 5) |
| Uptime: | 35:06:00 |
| Calls: | 1,266 |
| Files: | 1,362 |
| D/L today: |
3 files (6,742K bytes) |
| Messages: | 284,741 |