Hacker News new | past | comments | ask | show | jobs | submit login

Jumping to conclusions, are we?

Superuser.apk does not achieve root privileges and su does not blindly run your program with root privileges. su asks superuser.apk, if your program is allowed to run as root and only when superuser.apk agrees (and displays toast), then your program is run.

Also, the arbitrary privileges are reserved for setuid programs, which is not easy to achieve. Basically, su and Superuser.apk are gatekeepers to uid 0, which short of bugs, you can't get around.

Also, did you know, that you can disable adbd? Or remove root privileges from it?




You forget that init executes as root, and is therefore able to spawn root children.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: