5 comments

[ 3.1 ms ] story [ 26.7 ms ] thread
I know most people here hate that, but I think this makes a much stronger case for security by obscurity (not releasing the source code) in these changing times.

Of course security by obscurity by itself is by no mean sufficient.

> "A week of back and forth, 2.3 billion tokens, $2,283 in API costs, and about ~20 hours of me unsticking it from dead ends. It popped calc."

Corrent me if I'm wrong, I'm not a security researcher, but 20 hours, a week of work, 2283$ spent and over 2 trillion tokens, is not very 10x-ing as we were promised. Especially if you take into account that the guy is at least half capable for this take.

I dunno

people who can do this is supply constrained, now you can throw tokens at the problem and with nudging towards the goal you can get working exploit much faster, its probably not 10x but way faster than before
This has been what I’ve been screaming from the rooftops for a while, that these models can already do this.

Go read the devs actual blog though. This is more a statement on patch lag than anything else. In my mind that’s much more important than “zomg zero days!!!”

A security researcher instructed an LLM to write an exploit for a know bug fixed in an already published release

Not really impressive