Earlier quoted context omitted.
But the threshold between correct and incorrect inference is dependent on an intersection of the model and the document so far. That is not manageable by definition, I mean... It is a chaotic system.
Is this dissimilar to what the human brain produces? Are we not producing chaos controlled by wanting to give the right answer?
I used o3 to find a remote zeroday in the Linux SMB implementation
211–220 of 232 posts
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#212Earlier quoted context omitted.
All your content threads from the past months consist on you saying how much better OpenAI products are than the competition, so that doesn’t inspire a ton of trust.
Because in my use cases they are? Coding and math, science research are my primary use cases and codex with o3 and o3 consistently outperforms others in complex tasks for me. I can’t say a model is better just to appeal to HN. If another model is as good as o3 id use that in a second.
For example, I think 2.5 Pro and Claude 4 are probably better at programming. But, for debugging, or not-super-well-defined reasoning tasks, or even just as a better search, o3 is in a league of its own. It feels like it can do a wider breadth of tasks than other models.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#213Earlier quoted context omitted.
> I didn’t realise you’re an individual capable of designing and building complex systems made of multiple interconnected novel modules using only wireframes, and having all that work without any prior experimentation. Not really. It's just that there's a lot of prior works out there, so I don't need to do experimentation when someone has already done it and describe the lessons learned. Then you do requirement analy…
How do you handle work that involves building novel systems, where good prior art simply doesn’t exist? I’m currently dealing with a project that involves developing systems where the existing prior art is either completely proprietary and inaccessible, or public, but extremely nacient and thus documented learnings are less developed than our own learnings and designs. Many projects may have the primary objective of…
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#214Earlier quoted context omitted.
I realised I didn't mention it in the article, so in case you're curious it cost about $116 to run the 100k token version 100 times.
thank you, I was going to ask about this. It's not a crazy amount...
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#215Earlier quoted context omitted.
What exactly is disingenuous about it?
It reduces the value of a human life to the incremental rate at which they produce some concrete product. It is absurd.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#216Earlier quoted context omitted.
Using predictable systems. If your C compiler invents a new function call for a non-existent function while generating code, that's usually a bug. If an LLM does, that's... Normal. And a non-event.
And? What other engineering domain operates on a fundamentally predictable substrate? Even computer science at any appreciable scale or complexity becomes unpredictable.
An engineer doesn't just shrug and pick up slag because it contains the same materials as the original bauxite.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#217The most interesting and significant bit of this article for me was that the author ran this search for vulnerabilities 100 times for each of the models. That's significantly more computation than I've historically been willing to expend on most of the problems that I try with large language models, but maybe I should let the models go brrrrr!
I realised I didn't mention it in the article, so in case you're curious it cost about $116 to run the 100k token version 100 times.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#218Earlier quoted context omitted.
And? What other engineering domain operates on a fundamentally predictable substrate? Even computer science at any appreciable scale or complexity becomes unpredictable.
Every engineering domain operates within "known bounds". That makes it dependable. An engineer doesn't just shrug and pick up slag because it contains the same materials as the original bauxite.
We’re basically in the stone ages of understanding how to interact with synthetic intelligence.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#219We followed a very similar approach at work, created a test harness and tested all the models available in AWS bedrock and the OpenAI. We created our own code challenges not available on the Internet for training with vulnerable and non-vulnerable inline snippets and more contextual multi-file bugs. We also used 100 tests per challenge - I wanted to do 1000 test per challenge but realized that these models are not ev…
The blinders give you a problem in that a lot of security issues aren't at a single point in the code but at where two remote points in the code interact.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#220Earlier quoted context omitted.
How do you handle work that involves building novel systems, where good prior art simply doesn’t exist? I’m currently dealing with a project that involves developing systems where the existing prior art is either completely proprietary and inaccessible, or public, but extremely nacient and thus documented learnings are less developed than our own learnings and designs. Many projects may have the primary objective of…
Maybe the main problem is not solved yet, but I highly doubt that the subproblems are not. Because that would be cutting edge domain, which is very much an outlier.
> Most of my coding is fully planned to get to the end. The experiment part is on a much smaller scale (module level).
I would seem that these statements taken together mean you don’t experiment at all?