OpenSSH has the best track record, but even it had a zero-day RCE (regreSSHion) in 2024.
There are bound to be many more discovered as LLMs capable of doing so proliferate among those who don't report such things responsibly.
Keeping port 22 open puts you first in line for such exploits, while keeping it behind another layer (whether it's WireGuard or firewall tricks) would buy time, if not keep attackers away entirely. That seems useful, no?
Well yes - at least as things currently stand. It's interesting to me not for what it is right now, but what the trend might be. The extremes are probably something like:
1. Damp squib, goes nowhere. In 3 years' time it's all forgotten about
2. Replaces every software engineer on the planet, and we all just talk to Hal for our every need.
Either extreme seems reasonably unlikely. So the big question is: what are the plausible outcomes in the middle? Selfishly, I'd be delighted if a virtual assistant would help with the mechanical dreariness of keeping type definitions consistent between front and back end, ensuring API definitions are similarly consistent, update interface definitions when implementing classes were changed (and vice-versa), etc.
That's the positive interpretation obviously. Given the optimism of the "read-write web" morphed into the dystopian mess that is social media, I don't doubt my optimistic aspirations will be off the mark.
Actually, on second thoughts, maybe I'd rather not know how it's going to turn out...
> There's no way any business will handle business logic to a black box.
You mean, a black box like a programmer's brain? An AI backend will get used if it's demonstrably better on any dimension. The current iteration is no doubt a bit of a toy, but don't underestimate it.
It seems incredibly obvious that you could turn this into a real product, where the LLM generates the code once based on a high-level description of a schema and an API, and caches it until the description changes somehow.
GPT can generate thousands of lines of code nearly instantly, and can regenerate it all on the fly whenever you want to make a few tweaks. No more worrying about high-architecture designed to keep complexity understandable for mere humans. No code style guides or best practices. No need to manage team sizes to keep communication overheads small.
Then you train another AI to generate a fuzz test suite to check an API for violations of the API contract. Thousands of tests checking every possible corner case, again generated nearly instantly.
Don't underestimate where this could go. The current version linked here is a limited prototype of what's to come.
How many businesses operate at the whims of an Excel spreadsheet, hewing to the output of cell C1? A spreadsheet who's creation myth sits alongside a departed founder and no one really knows how it works.
People already do need it! In the US alone, about a half million people are on dialysis. There are many health and functional consequences to both intermittent and peritoneal dialysis; they are not exactly benign treatments.
The major benefit to implanting it under the skin, as we do with pacemakers, is that doing without permanent holes or tubes through the skin reduces infection risk.
Consider also the danger of having something dangling from your body that is powered by your arterial blood pressure (from a major artery, as the kidney is). A trip and fall could be instantly fatal.
I had a kidney stent in for a few days while I healed from an operation. Let me tell you, it’s a huge quality of life downer (obviously the medical operation outweighed the life style concern). You definitely don’t want medical equipment dangling on the outside of your body if you can help it.
Popular shareware proggies like "Xara3D". Don't think they'd qualify as modeling software. They had basic rotate/translate/scale transform routines in them plus glitzy effects.
(Note "shareware" usually meant cracked as far as youthful hobbyist website building from basements and bedrooms was concerned.)
There were some people who made 3D animated gifs of diverse subjects for a living (e.g. The Animation Factory). I am sure they used real 3D modelling, animation and rendering software for that.
The video evidence of the L-form switching is no doubt very interesting, but a more accurate headline would be “One cause of resistance to certain antibiotics in UTIs identified.” Or the original article’s title, which is “Possible role of L-form switching in recurrent urinary tract infection”; see https://www.nature.com/articles/s41467-019-12359-3
I would love to see data on how common this phenomenon is in various populations of UTI patients (elderly, young, inpatient, outpatient, etc), given different prior exposures to antibiotics; for now it looks like 30 patients were assessed.
There are obviously many different causes of resistance previously identified, going all the way back to penicillinase enzymes inactivating penicillin. As often happens with lay summaries, this makes it sound a little too much like the cause of all antibiotic resistance has been found.
Other known causes of antibiotic resistance include the formation of biofilm -- essentially a colony of bacteria -- and rapid genetic mutation in the face of harsh conditions.
Well, for starters, it's hard to get 200 people who might be eligible for life-preserving surgery to volunteer to possibly get a sham procedure for the exclusive benefit of othewars; not to mention build a team of surgeons, hospitals, etc. willing to do the trial; and someone to pay for millions of dollars in treatment and administrative costs. Clinical trials involving surgery, especially with sham procedures as a proper control, are exceedingly rare in the US for these reasons. (this is discussed in the OP itself.)
So what good does increasing US medical school graduation rates do? OK, it would displace some IMGs/FMGs from residency positions, but it doesn't ultimately create more doctors. You can't be licensed to practice independently in the US unless you enter a residency, take the USMLE Step 3 after intern year, and typically you also take a specialty board exam at the end of residency.
There are bound to be many more discovered as LLMs capable of doing so proliferate among those who don't report such things responsibly.
Keeping port 22 open puts you first in line for such exploits, while keeping it behind another layer (whether it's WireGuard or firewall tricks) would buy time, if not keep attackers away entirely. That seems useful, no?