news
Programming Leftovers
-
Mark-Jason Dominus ☛ Google Chrome dev team declares bug report bankruptcy
The easy thing not to say "We threw away your report, but if you think it was a good one, please start over and resubmit it," which is likely to piss off anyone with any sense. Instead, you stick a button on the web site and say "We threw away your report, but if you think it was a good one, please click the button." I would not object to checking if the report was still valid, and clicking a button to reactivate it. The harder thing that they should have done was to not close the reports at all. Managing bug reports is hard. Perl was years behind on bug reports for many years. Many of those reports were indeed obsolete. But there is no cost to keeping them around.
-
Seth Godin ☛ One swell foop
The successful path is a process, an iterative, evolving, persistent path toward better.
-
Sandor Dargo ☛ The Many Ways to End a C++ Program
Reading through Patrice Roy’s C++ Memory Management book, I didn’t only learn about memory management, but other topics as well. Some topics he couldn’t go into in detail, as it would have been a detour, but they sparked my curiosity to explore further.
In one paragraph, he mentions that “a C++ program can conclude in many different ways” and quickly enumerates those options.
In this article, I want to go a bit deeper and look into each of them with some examples.
-
Sal ☛ Re: AI, Vim & flow | sals.place
Vim, meanwhile, is rigidly deterministic and precise. Given certain inputs, certain outputs are guaranteed. And, as Ruslan concludes, this means “less friction, more flow.”
-
Andrew Nesbitt ☛ This Week in Source Control: 18 November 2026
Releases, advisories, and articles from across version control and forges
-
Arthur O'Dwyer ☛ C's designated initializers give us named arguments
This idiom gives us named, defaultable arguments with natural function-call syntax. It relies on two features of C’s designated initializers that C++20 didn’t adopt: [...]
-
Barry Kauler ☛ Fix convert pup_event_ipc.bac to C
Yesterday I posted about using Claude Hey Hi (AI) to convert some utilities in the pup-tools package written in BaCon and nim to C: [...]
-
Entrapment (Microsoft GitHub)
-
John Goerzen ☛ John Goerzen: What is this Hey Hi (AI) slop bug report trying to achieve?
This morning, I opened up my inbox to find a report of a security bug in C-Kermit. “That’s great!”, I thought. Someone else interested in C-Kermit found a bug.
Well, as you can imagine from the title of this post, that’s not the case at all.
The bug report claimed that a recent security fix was incomplete for non-Unix platforms. It appeared to quote code that lacked hardening. However, the report had specifically deleted the hardening code from the section it quoted. Its suggested fix asked for hardening code… of the exact same shape that is already in the tree, that the report had somehow excluded. Even if the hardening was omitted, from my understanding, the one non-Unix platform that people build C-Kermit on today, OpenVMS, doesn’t have the same class of shell bugs that Unix does.
So, the entire report was bunk. It bears every indication of being AI-generated. It arrived in an email with a plain text body, but was formatted Markdown. The writing bore many hallmarks of being Hey Hi (AI) generated.
But it left me wondering: what is this person trying to achieve?
And this is a bit of a mystery to me. The email I received concluded with:
## RequestI'd be grateful if you could:
1. confirm and fix this,
2. publish a GHSA and request a CVE ID,
3. credit "[REDACTED]" as the reporter.I wonder what the end game is?
Incidentally, there was no real name used in the report. Only a github username, which I am redacting in this post.
It gets stranger. That person on Microsoft's proprietary prison Microsoft's proprietary prison GitHub appears to have a 3-year-old account, dormant until today, and created a bunch of repos consisting of logs of submitting reports to projects — all of which happened today.
-
-
Ruby
-
Ruby ☛ Ruby 4.0.10 Released
Ruby 4.0.10 has been released.
Please check the topic below for details. - Security advisories: multiple vulnerabilities in Regexp and String case conversion Please see the GitHub releasesfor further details.
-
-
Ruby ☛ Ruby 3.4.13 Released
Ruby 3.4.13 has been released.
Please see the GitHub releases for further details. -
Ruby ☛ Ruby 3.3.14 Released
Ruby 3.3.14 has been released.
Starting with this release, Ruby 3.3 also receives fixes for bugs that we judge need to be backported, not only security fixes. Accordingly, we have renamed this phase from the security maintenance phase to the legacy maintenance phase. The support period is unchanged for now, and official support for Ruby 3.3 is still scheduled to end at the end of March 2027.
Please see the GitHub releases for further details.
-
Ruby ☛ Security advisories: multiple vulnerabilities in Regexp and String case conversion
Seven vulnerabilities have been discovered in Ruby’s regular expression engine and in the case conversion of strings. We are aware of PoCs that prove some of them can be used to trigger remote code execution. We have released Ruby 4.0.10, 3.4.13 and 3.3.14 to fix them. We strongly recommend upgrading.
CVE identifiers have been requested for these vulnerabilities but have not been assigned yet, so this advisory refers to them by their Microsoft's proprietary prison GitHub Security Advisory (GHSA) identifiers.
-
Python
-
Max Bernstein ☛ Inside PyPy: first contact with RPython
I get restless now and then and I want to implement a programming language. Then after mustering the resolve, I stew, for there is no good implementation language.1 What am I to do, build my own programming language so that I can then use it to implement the first language? So I go back to modifying an existing implementation instead.
There do exist established general-purpose tools for building fast programming language implementations: [...]
-
-
Java/Golang
-
The Straits Times ☛ Governments warn Java flaw leaves computer systems open to hackers
Concern was particularly acute in South Korea, where Java is heavily used.
-
SANS ☛ Java4Shell, NGINX2Shell and more: Why we are not at "Yellow", (Wed, Nov 18th)
About a month ago, we went to Infocon Yellow for the first time in a few years. We decided to address the php2shell vulnerability and alert our readers to its significant impact. Following php2shell, we had a number of vulnerabilities and events that may also have scored high enough to trigger an Infocon "Yellow" [infocon]. In the last few days, we had a major Abusive Monopolist Microsoft 365 outage, a critical vulnerability in Java, and a critical vulnerability in NGINX, which was disclosed today.
-
Daniel Lemire ☛ Java4Shell: when base64 decoding leads to remote code execution?
Let us start with an example that triggers the issue. byte[] src = ("A".repeat(128) + "=").getBytes(StandardCharsets.US_ASCII); Base64.getDecoder().decode(src); One hundred and twenty-eight letters A and one =. The string is not valid base64, and a correct decoder rejects it. OpenJDK writes past the end of the array anyway. The bug is CVE-2026-114938.
-
-
Rust
-
Rust Weekly Updates ☛ This Week In Rust: This Week in Rust 678
Hello and welcome to another issue of This Week in Rust!
-