Timeline for What are the security disadvantages of rooting an Android phone?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 17, 2012 at 19:03 | comment | added | Matthew Read | @MarcoW SuperUser is released by Chainfire here; coupled with that official release you should be able to analyze any root method and do it yourself, at least if they've made the details available. That really is the crux of security issues, though: You have to trust someone else in order to gain anything from them. Nothing we can do about that. | |
Apr 17, 2012 at 13:27 | comment | added | caw | This is the problem. The sources for rooted Android are always normal forums with users who made them independently. So how can you be sure to get a non-malicious package? You can't. | |
Apr 16, 2012 at 17:05 | comment | added | Matthew Read | @MarcoW. You can't, just like you can't be sure that the binary isn't malicious or that the browser isn't malicious or that every last but of Android is Google trying to steal your secrets :P. If you don't trust your source, don't trust the software you get from that source. | |
Apr 15, 2012 at 21:57 | comment | added | caw | How can we be sure that the SuperUser app is not the one that is malicious? (Not refering to a special app, just asking in general.) | |
Sep 27, 2011 at 18:42 | comment | added | Broam | @LanceBaynes It's a version of the SuperUser application, which comes with its own su binary that screens requests for root access - you must approve the access before the app gets root. | |
Sep 27, 2011 at 17:48 | comment | added | LanceBaynes | sry for asking, but what the hell is a "superuser 3.x" - is it binded to an Android version? | |
Sep 27, 2011 at 15:34 | history | answered | Matthew Read | CC BY-SA 3.0 |