News for hackers. Stuff that matters.
Re:Someone reported java4shell bug in September 2026 by rfgplk on Thursday November 19, 2026 @10:26AM (#50561336)
> From califio: "I focused the audit on the JIT compiler, intrinsics, widely accessible APIs, and cryptography. Well, more precisely, I told Codex to look at those areas like any serious security researcher in 2026."

I have no idea why people keep talking like this. Probably because sadly most engineers lack the ego to back themselves up. Imagine if someone said this in 2015: "I worked on the physics engine, tests, via widely accessible libraries. Well, more precisely, I told my compiler to read the source code and compile it like any serious software engineer in 2026."

Quit saying Codex/Claude/an LLM did something. They didn't. You did.

Re:Someone reported java4shell bug in September 2026 by NooneAtAll5 on Thursday November 19, 2026 @10:31AM (#50561416)
no, it's more like "I worked on physics engine. Well, more precisely, I used already made library and never even looked at actual physics"
Re:Someone reported java4shell bug in September 2026 by p-e-w on Thursday November 19, 2026 @10:34AM (#50561468)
A frontier AI is nothing like a compiler. The litmus test is how much expertise was required to get it to find the results. If a basic prompt brings up an industry-shaking vulnerability of this caliber, then the human was at best a janitor.
Re:Someone reported java4shell bug in September 2026 by Izkata on Thursday November 19, 2026 @01:13PM (#50563755)
For me it's whether or not they've started committing prompts instead of code.
Re:Someone reported java4shell bug in September 2026 by LoganDark on Thursday November 19, 2026 @10:36AM (#50561485)
> Quit saying Codex/Claude/an LLM did something. They didn't. You did.

I think there's a vast difference between giving source code to a compiler (even a superoptimizing compiler) and giving a prompt to a language model. This distinction absolutely deserves to be called out and not swept under the rug.

Re:Someone reported java4shell bug in September 2026 by xmodem on Thursday November 19, 2026 @10:45AM (#50561630)
"I worked on the physics engine, tests, via widely accessible libraries." is a nonsensical sentence as written, but a colleague who told me they had done this would be telling me a vastly different thing to if they had told me they had compiled the source code to a physics engine.

There is a massive difference between prompting "security audit this codebase, make no mistakes", performing an in-depth agent or LLM-assisted focused search for security relevant code, or otherwise manually reviewing code as we did in the pre-LLM era. It behooves us to be honest about our own personal contribution to our output - both towards others and to ourselves.

Re:Someone reported java4shell bug in September 2026 by tkz1312 on Thursday November 19, 2026 @11:13AM (#50562003)
I don't disagree with you necessarily, and I do think it a good practice to disclose how much of a contribution was llm generated, but regarding the difference an individual makes, I see a huge gap between different colleagues in how well they are able to use llms and the quality of the results they are able to produce with them, so I am increasingly inclined to view them as something closer to a compiler or SMT solver than a contributor in of themselves.
Re:Someone reported java4shell bug in September 2026 by boie0025 on Thursday November 19, 2026 @12:57PM (#50563522)
I am also finding this disparity. I hand off the agent skills I use daily, to produce the results I want in the way I want them, to some people and I still get poor results, and others I get good results. There's something about a combination of tools, prompting and FTGs about the outcomes that combine into these different results. I should imagine at some point that will disappear?
Re:Someone reported java4shell bug in September 2026 by tkz1312 on Friday November 20, 2026 @05:00AM (#50572500)
why should it disappear? afaict llms seem to be an accelerant, skilled engineers with a good grasp of how to use then fly, mediocre ones, or ones who haven't yet figured out workflows that mesh with their style kinda just chug along at their same old pace.
Re:Someone reported java4shell bug in September 2026 by wat10000 on Thursday November 19, 2026 @11:16AM (#50562051)
Is it really fair to say that I did something when my contribution was typing straightforward English prose for thirty seconds and then letting it run?

Your hypothetical makes the opposite point from what you intend. If someone in 2015 said that they worked on a physics engine, and all they did was run the compiler on existing code, we'd laugh them out of the room. Pointing an existing computer program at existing work doesn't count as doing very much.

Re:Someone reported java4shell bug in September 2026 by ShinyLeftPad on Thursday November 19, 2026 @02:56PM (#50565410)
It's an honest disclaimer of jerk behavior "i didn't care to review it carefully, you do it".

Because when people really spend the effort required to fully review and own the result, somehow they don't have a problem of pointing at models.