ChanServ changed the topic of #asahi-re to: Asahi Linux: porting Linux to Apple Silicon macs | Hardware / boot process / firmware interface reverse engineering | WARNING: this channel (only) may contain binary reverse engineering discussion | RE policy: https://alx.sh/re (MANDATORY READ) | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-re
PhilippvK has joined #asahi-re
phiologe has quit [Ping timeout: 480 seconds]
skipwich has quit [Ping timeout: 480 seconds]
<marcan>
lol
<Graypup_>
inb4 another "<marcan> I don't know what <...> is; <marcan> aaand that's a macOS CVE. hoo boy." hahaha
<dougall>
(fwiw agx firmware has similar 'this probably isn't, and definitely wasn't, a security boundary' features)
<dougall>
(although i'm perhaps misunderstanding the dcp/carveout system threat model, so to be explicit, i believe xnu can read and write agx firmware memory by design)
<marcan>
dougall: I think the idea of locking down coprocessor firmwares in iBoot is kind of an afterthought in this iteration
<marcan>
I don't think they're particularly seriously trying to make them resilient to AP meddling, at least not yet
<dougall>
yeah - that sounds right, I guess it's nice for experimentation for now at least :)