Earlier quoted context omitted.
How would you value this exploit, or any exploit?
I understand this is arbitrary code execution with root access. I'm imagining the potential of infecting a high status individual and I think a bad actor would pay millions for such an exploit.
I hacked macOS
111–120 of 140 posts
Re: I hacked macOS
#112Any suggestions for how I can get to anywhere close to Lina's skills? It's just mad skills.. I don't believe simply putting in huge amount of time in front of the machine is adequate. Neither is simply being smart. Is it just a combination of being smart, sinking in a lot of time, interests etc?
Read computer architecture and computer systems books.
Re: I hacked macOS
#113Earlier quoted context omitted.
[flagged]
> Lina is a pseudonym for Marcan Is there any evidence for this? I've seen a bunch of people say it on HN.
Finally, and my personal favorite: Asahi’s VTuber reveal was by “hacking” and hijacking one of Marcan’s streams. The introduction was literally replacing Hector.
Re: I hacked macOS
#114Re: I hacked macOS
#115Re: I hacked macOS
#116Earlier quoted context omitted.
It's clearly a slide deck for a conference presentation or something. So yea, it's terrible for a web page.
I don’t think it’s a presentation. It’s multi dimensional. No one’s navigating multiple dimensions while presenting.
Re: I hacked macOS
#117Earlier quoted context omitted.
Read computer architecture and computer systems books.
Any suggestions? I'll start with something that might be a good beginner friendly way to get familiar with some of the concepts: 'The Soul of a New Machine' by Tracy Kidder.
Re: I hacked macOS
#118Earlier quoted context omitted.
[flagged]
> Lina is a pseudonym for Marcan Is there any evidence for this? I've seen a bunch of people say it on HN.
Re: I hacked macOS
#119Lina is not a random emerging VTuber who randomly stumbled upon the bug and found an exploit technique that can be applied to exploit the bug; she is actually highly skilled at exploit things...
Re: I hacked macOS
#120From code comments, what I understood (most likely in an incorrect way) is: - Use Metal shader code to make process page table accessible to shaders via page protection layer bug exploited using return oriented programming (ROP) - Use Metal shader code to acquire read/write access to physical memory - Use Metal shaders to access the kernel page table - Deals with ASLR to find the kernel base address - Obtains process…
You’re pretty much correct. GPUs are a very interesting attack vector. Especially as more computation is being pushed to GPUs, and they’re not always well isolated.