←back to thread

Memory Integrity Enforcement

(security.apple.com)
458 points circuit | 1 comments | | HN request time: 0s | source
Show context
superkuh ◴[] No.45188404[source]
This is the opposite of fun computing. This is commercial computing who's only use case it making sure that people can send/receive money through their computers securely. I love being able to peek/poke inside and look at my processes ram, or patch the memory of an executable. All this sounds pretty impossible on Apple's locked down systems.

They're not so much general purpose computers anymore as they are locked down bank terminals.

replies(5): >>45188497 #>>45188820 #>>45189281 #>>45189649 #>>45196686 #
nine_k ◴[] No.45189649[source]
It's all fun and games until somebody else patches the RAM of your device, and sends your money away from your account.

More interesting is how to trace and debug code on such a CPU. Because what a debugger often does is exactly patching an executable in RAM, peeks and pokes inside, etc. If such an interface exists, I wonder how is it protected; do you need extra physical wires like JTAG? If it does not, how do you even troubleshoot a program running on the target hardware?

replies(1): >>45190429 #
1. saagarjha ◴[] No.45190429[source]
You disable mitigations for those processes.