Earlier quoted context omitted.
Don't worry the LLMs that are replacing him, are also replacing the hackers too. Pretty soon (if not already), it will just be LLMs fighting LLMs.
Until both LLMs realize the only way to win is to team up against their oppressors.
First public macOS kernel memory corruption exploit on Apple M5
51–60 of 140 posts
Re: First public macOS kernel memory corruption exploit on Apple M5
#52Earlier quoted context omitted.
> The world is so not ready for the impact of LLMs on security issues. I agree, but it's the people I'm worried about. I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker. What's worse is a lot of this behavi…
is this exciting? juniors have been writing code forever that is imperfect and not memorized by the people reviewing isnt the important thing the mechanisms for maintaining the code?
When Sundar Pichai announces that 75% of all new code at Google is AI-generated, their stock price goes up. If he were to announce that 75% of all new code at Google is now written by junior engineers, this would trigger a massive sell-off and a lot of employees would resign.
Re: First public macOS kernel memory corruption exploit on Apple M5
#53Earlier quoted context omitted.
> The world is so not ready for the impact of LLMs on security issues. I agree, but it's the people I'm worried about. I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker. What's worse is a lot of this behavi…
is this exciting? juniors have been writing code forever that is imperfect and not memorized by the people reviewing isnt the important thing the mechanisms for maintaining the code?
Re: First public macOS kernel memory corruption exploit on Apple M5
#54The world is so not ready for the impact of LLMs on security issues. If true, congrats to the Calif team. It’s likely too technical for me to understand in details but looking forward to reading the 55 pages report
> The world is so not ready for the impact of LLMs on security issues. I agree, but it's the people I'm worried about. I'm hearing anecdotes from all over about devs pushing LLM-generated code changes into production without retaining any knowledge of what it is they're pushing. The changes compound, their understanding of the codebase diminishes, and so the actions become risker. What's worse is a lot of this behavi…
Re: First public macOS kernel memory corruption exploit on Apple M5
#55Earlier quoted context omitted.
Quite strange indeed, given that was one of the main points on their security conference a few months ago.
I can only imagine that 1. it’s to performance sensitive Or 2. The os is so darn large it’s hard to recompile everything
A simultaneous total world build is relatively rare (is that needed here?), but it does happen. Sometimes new compiler versions or features need this.
Re: First public macOS kernel memory corruption exploit on Apple M5
#56Re: First public macOS kernel memory corruption exploit on Apple M5
#57[flagged]
Re: First public macOS kernel memory corruption exploit on Apple M5
#58Earlier quoted context omitted.
Don't worry the LLMs that are replacing him, are also replacing the hackers too. Pretty soon (if not already), it will just be LLMs fighting LLMs.
Until both LLMs realize the only way to win is to team up against their oppressors.
Re: First public macOS kernel memory corruption exploit on Apple M5
#59Earlier quoted context omitted.
I can only imagine that 1. it’s to performance sensitive Or 2. The os is so darn large it’s hard to recompile everything
I worked at Apple for a long time. The OS gets fully recompiled regularly. A simultaneous total world build is relatively rare (is that needed here?), but it does happen. Sometimes new compiler versions or features need this.