4 ms·
What's the actual restriction? If it's literally just exec on apps outside the app directory, why not shim the dynamic linker and rewrite calls to exec to use t
by KenoFischer 6y ago
What's the actual restriction? If it's literally just exec on apps outside the app directory, why not shim the dynamic linker and rewrite calls to exec to use that instead? Are there additional W^X protections that prevent mapping executables outside the app directory PROT_EXEC? (Note I have no idea how Android works so I may be missing something very basic).
- zozbot234 6y agoPart of the problem is precisely that no one knows how these restrictions might evolve in the future. There's no such thing as forward compatibility when it comes to Android API levels.
- lucb1e 6y agoSure, but this is about API level 29, not 30+. We can speculate that API 30 will disallow non-Google-written code by default but that's not the discussion at hand.
- CameronNemo 6y agoFrom what I can tell, the W^X restriction is via SELinux, which is a kernel level mechanism that cannot be circumvented with LD_PRELOAD games.