4 ms·
I wonder how many years we've got where you're still able to read the big mega archive... Someday it may sit in some kind of "protected enclave", mapped into y
by jlokier 6y ago
I wonder how many years we've got where you're still able to read the big mega archive...
Someday it may sit in some kind of "protected enclave", mapped into your process with "execute-only" permission for code, and maybe graded protections for its data as well, so you can't debug, trace, instrument, reverse engineer or otherwise get to really know the system libraries to see what they are doing and learn from them.
The trend has been that way for a while. For the moment, that kind of isolation is done at process boundaries, on devices that have enclaves.
There is no technical reason why that kind of isolation cannot extend inside processes, for a company that designs its own CPUs. For the same kind of "black boxes" as we already have inside mobile devices, but with faster API calls and data exchange than doing it across processes boundaries.