@ColinTheMathmo I had quite a few enquiries of this kind when the Log4j vulnerability happened five years ago. I've been expecting at least one or two about PHP.
(I'm secretly hoping someone will demand I check that PuTTY makes no use of the number 4…)
@simontatham Our leaked credential finder has identified a compromised private key in your software. Please fix immediately !!11!oneone!!1!
@elricofmelnibone @simontatham
No, it's 4, not 1 or 11. Remarkably close guess, though.
Oct 30, 2026, 9:00 PM
@simontatham @ColinTheMathmo Barry gets these all the time... https://bsky.app/profile/blowdart.me/post/3mykhiherrk2m
@simontatham @ColinTheMathmo This is the lot for software producers in general. Those of us old enough to remember were flooded with demands to submit Y2K affidavits. Whenever there's a widely-known (or predicted, or just hypothesised) bug or bug class, users want to be reassured, and many of them have no clue what's going on "under the bonnet", as it were.
Gets in the way of the real support requirements, of course!
Ooo, flashback to all the Y2K demands for certification, especially for our VTxxx terminals.
Oct 30, 2026, 10:54 PM