Running a rooted G2 here, and I just installed the new US Bank app (com.usbank.mobilebanking). Upon initial launch, it requests root. If I deny the request, it looks like it would still work, but I'm concerned about what they would attempt to do with it if granted, and why they feel a need to do so. I haven't pulled logcat info yet, but I have a screenshot of the superuser request as proof.
Any thoughts? Here's mine:
Where did you download it from?
What permissions does it list?
LOL...
this had me cracking up...
I dont think I would be installing this one..
funny... nice catch
Most likely the same **** as the Blizzard Authenticator. With a rooted device, you can steal the applications /data and restore it onto another device, thus stealing *your* settings.
An application CAN refuse to run if it finds your device is rooted, whether you accept or deny the root request, and there is nothing stopping the application reporting back IMEI/IMSI and any other default stuff.
For clarification, this is the official app from US bank. I was informed about it from my bank when I logged in from the computer, and they provided a qr code pointing at com.usbank.mobilebanking on the market. I'm working on a cyanogenmod build machine, and I'm gonna look into figuring out a way to change the way superuser works to provide a third option to give the app a fakeroot style environment with a full transcript of commands run, and their output. I'm inclined to doubt my bank would pull anything really stupid with it, but then, you'd think sony would have been smarter than to rootkit peoples machines with audiocd's so many years ago too... At the least, there should be an easier way to answer the question "what is that app trying to do with a root shell?"
Ended up looking at it through dedexer. It seems a company called mcom created at least parts of the app, and their library has functions for detecting and logging to logcat rooted device status and weather the input method is custom or not. I suspect that these mcom functions are called based on policy from the bank in charge of a particular app, because I can't seem to get it to request root anymore. It appears that when it did, all it would have done is immediately destroyed the root shell and logged a warning to logcat.
fwiw, the way I was able to do it looked something like this:
$ java -jar ddx1.15.jar -d mobilebanking classes.dex
$ cd mobilebanking
$ grep -r \"su\" *
A custom su with fakeroot and logging via a third option would be neat though... I might still work on that.
acolwill said:
Most likely the same **** as the Blizzard Authenticator. With a rooted device, you can steal the applications /data and restore it onto another device, thus stealing *your* settings.
An application CAN refuse to run if it finds your device is rooted, whether you accept or deny the root request, and there is nothing stopping the application reporting back IMEI/IMSI and any other default stuff.
Click to expand...
Click to collapse
While I still have a method to figure out what an app would do with root fresh in my mind, I'm gonna take a look at that there Blizzard Authenticator... I've never used it, as Blizzard is on my do not trust list, and I think this might be interesting....
Blizzard's auth seems to do the same basic thing. It has a function called "isDeviceRooted" which seems to return true any time the su command can be run, though it nags the user for having root.
I started working on a custom su setup which allows you to log what programs try to do as root. So far, that entails recompiling the su binary, as well as busybox. It's in rough shape yet, so current "release" will just be a pastebin dump here:
http://pastebin.com/fiqQPeFq <- patch to su.c to use a logfile
http://pastebin.com/37NJyxQh <- new busybox config with support for the 'script' command used by my custom su, along with a few other small changes.
If you can compile it, you should be able to figure it out as well. Once I can make it a little cleaner (eg, logging as a checkbox on the accept/deny screen, instead of always being done), I'll make a more proper release, but maybe someone will find it useful here.
Hello,
I have a question about how the "superuser"-app works behind the scenes.
As far as i know: The "superuser"-app can be used to grant root-permissions only to the programs, that I want. All other programs are still not running in root. Is this right?
If I'm right on that... Why does only the app super-user does have root after rooting the phone via e.g. the zergrush-exploit and other apps still not have root permissions although the phone has been rooted? Isn't there a security gap ?
In my point of view it could be possible, that any other app could take the root-rights just like the app "superuser" does it. If I'm not right, I don't get it, why only "superuser" gets root and all other apps can't get root unless "superuser" gives them root...
Isn't it a security gap? I just don't get it... how is this achieved?
Is it absolutely (or nearly absolutely) safe, that no other programs can get root-permissions when I use "superuser"? As I already said before, I'm really curious about, why or how this can be achieved and "guaranteed"...
Thanks in very much advance.
Kind regards
mr. salt
I think it's barely possible, that I'm the only one who is interessted how this app is working or wondering about the same security issues, which come along with my questions above?
I would appreciate an sophisticated answer very much!
greetings
mr. salt
sea_salt said:
Hello,
I have a question about how the "superuser"-app works behind the scenes.
As far as i know: The "superuser"-app can be used to grant root-permissions only to the programs, that I want. All other programs are still not running in root. Is this right?
If I'm right on that... Why does only the app super-user does have root after rooting the phone via e.g. the zergrush-exploit and other apps still not have root permissions although the phone has been rooted? Isn't there a security gap ?
In my point of view it could be possible, that any other app could take the root-rights just like the app "superuser" does it. If I'm not right, I don't get it, why only "superuser" gets root and all other apps can't get root unless "superuser" gives them root...
Isn't it a security gap? I just don't get it... how is this achieved?
Is it absolutely (or nearly absolutely) safe, that no other programs can get root-permissions when I use "superuser"? As I already said before, I'm really curious about, why or how this can be achieved and "guaranteed"...
Thanks in very much advance.
Kind regards
mr. salt
Click to expand...
Click to collapse
Ok let me see if I can explain this the best way I can. When you root your phone you are giving yourself the ability to run apps that require root. This ability is turned off by default in android. Now lets compare this to Linux, when you run an app as root you have t run the sudo command and then enter your password each and every time you want to run it with rooted rights. SuperUser is an app that when prompted will remember the selection you choice so you dont have to allow it every time you run the app and with out opening a terminal to type the commands to allow it to run as root.
You are looking at the app of super user more as a stand alone app instead of being a front end UI for the commands that you would have to run to get the same out come.
As for the security, to be honest the best security is common sense. As it is a simple fact that PC, phone, internet, server ect security is only as good as the hacker trying to get into it. If he/she really wants your info they are gonna get it. Take a look at what happened to the US DOD and they have a far more secure setup then anything on the market.
This in my honest opinion is a excellent idea. And wish they would of done it along time ago.
Many of you may not give it a second glance, but among all the furor and concern about permissions requested by market apps and privacy, all Custom ROMs (CyanogenMod included) ship with one major security risk — root!
We have been struggling with how to handle this for quite a bit, and took a first step with the first public CyanogenMod 9 alpha builds, by disabling the previously-default root access over USB. You can still get adb root access by running “adb root” in terminal, should you ever need it.
We recently merged 3 patches into CyanogenMod 9, to further address this: http://goo.gl/eCjDV http://goo.gl/oWAFI and http://goo.gl/34vai.
What follows is an explanation of the changes, how they affect you and our reasoning behind them.
What do the patches do?
They disable root selectively and in a configurable way. Users will be able to configure their exposure to root as:
Code:
Disabled
Enabled for ADB only
Enabled for Apps only
Enabled for both
How does this change affect the usage of your device, and root apps you have installed?
On a default CyanogenMod installation, root usage will have to be explicitly enabled by the user. This means that the user is fully aware that any application that uses root may perform actions that could compromise security, stability and data integrity. Once enabled, the process mirrors that of the current process, apps that request root will be flagged by the SuperUser.apk and the user will have to grant selective access.
Why the change?
At CyanogenMod, security has always been one of our primary concerns, however, we were hesitant to make a change that might disrupt the current root ecosystem. With CyanogenMod 9 we have the opportunity to do things better, whether its the code in the OS, UI/UX, or security – we are taking this time to do things with a fresh approach.
Shipping root enabled by default to 1,000,000+ devices was a gaping hole. With these changes we believe we have reached a compromise that allows enthusiasts to keep using root if they so desire but also provide a good level of security to the majority of users.
What concerns remain?
Many of you reading this are savvy enough to note a remaining hole in this approach – recovery and unlocked bootloaders. The bootloaders are out of our hands, there is little to nothing we can do on that front.
Regarding recovery – with unlocked bootloaders, a malicious user could just flash a new recovery image (without any potential security we could apply) or just dump the data partition. This however, requires physical access to the device. As such, the security standards for this are highly reliant on you, the device owner. Data encryption is available in ICS to safeguard your data. (Warning for emmc only users – encrypted /data means recovery will be non-functional.)
The onus is on you to secure your device; take care of your possessions, and this risk is minimal. Always make sure you take devices out of your car before you go into the mall and remove them from pockets before washing laundry. Common sense is a basic security tool.
But Why?
We honestly believe there are limited uses for root on CyanogenMod, and none that warrant shipping the OS defaulted to unsecured.
Click to expand...
Click to collapse
Hope it works out for them, I think it's a pretty good idea.
Sent from my HTC Glacier using xda premium
It better be easy to reactivate because last time i checked, you need root to change ur rom
Sent from my HTC Glacier using XDA
THEindian said:
It better be easy to reactivate because last time i checked, you need root to change ur rom
Sent from my HTC Glacier using XDA
Click to expand...
Click to collapse
1) it's a setting in the OS, you either pick ADB only / APP only or / Both
2) you still physically still have root access. You'll still have s-off, and have SuperUser in the /bin or /xbin file system.
3) this just allows people who what Cyanogen Mod on their phone to get it w/o having to worry about security risk of applications running SU access and damaging something.
4) this could/may/will pave the way for OE manufacturers to incorporate a similar feature into their OS shipping from the factories.
i actually find this a good idea for new comers, so that they don't mess up their devices
I'm glad to see this. Needlessly running with root access at all times can be a big security issue.
THEindian said:
It better be easy to reactivate because last time i checked, you need root to change ur rom
Sent from my HTC Glacier using XDA
Click to expand...
Click to collapse
not true, all you need is custom recovery which can be flashed via fastboot, i have s-on with cwm recovery and went from stock rom to ics
edit: + This is a good approach for newcomers
First off, great forum, tons of awesome information.
I apologize in advance as I am sure these questions have been answered a million times but being new to a Rooted device, I'm looking for a little clarity and guidence.
I have the AT&T variant of the LG G3, awesome awesome device.
I rooted the device with Stump Root (doesn't get any simplier then that)
I then installed "Xposed Installer", "Titanium Backup", "SuperSu", and "G3 Tweak Box".
Questions,
Xposed
1) Seems pretty straight forward, is there anything as a newbie I should know, avoid, lookout for?
Titanium Back Up
1) Well, it all looks like chinese to me. First off, I have backed up all my apps, but when I check "Backup/Restore" I still see certain apps as "No Backup Yet". Why?
2) Also, how often should I backup the apps? Is once enough?
3) After backing up bloatware, is it then safe to remove and delete?
4) Schedules, should I be enabling either option?
5) Main Menu, whats the most important actions to take here?
SuperSu
1) Seems fairly straight forward, what are "logs" and do I need to pay attention to them?
2) Settings, is there any options I need to change, take advantage of? Anything I should avoid tampering with?
Misc Questions
1) When system updates come out, will this cause me to lose Root access, if so why and how do I avoid that?
2) Is there any prevenitive measures that I need to take to protect my device against any crashes, bricking, or any other general screw ups a newbie might cause with Root access?
3) Also, how do I not destroy my device while learning to take advantage of Root access?
4) In addition to what I have already installed, is there any other must have apps for the Rooted user?
I appreciate any & all help, thanks alot in advance!
I'll answer what I can, as best I can.
Vic098 said:
Xposed
1) Seems pretty straight forward, is there anything as a newbie I should know, avoid, lookout for?
Click to expand...
Click to collapse
Make sure you have BusyBox installed as well.
It's best to change one setting at a time. It's tedious, especially if you have to reboot after changes, but if something goes awry, it's much easier to track down the conflict or bug, especially if you're using multiple modules.
Titanium Back Up
1) Well, it all looks like chinese to me. First off, I have backed up all my apps, but when I check "Backup/Restore" I still see certain apps as "No Backup Yet". Why?
Click to expand...
Click to collapse
There's a definite learning curve with TB. I'm not sure why some apps might not back up. It could be because they're core components of the OS and are write protected.
2.) Also, how often should I backup the apps? Is once enough?
Click to expand...
Click to collapse
When talking about batch backups, "enough" is at your discretion. No harm in doing them periodically, especially if you install a bunch of new apps. Backing up individual apps is good to do before updating them, in case you decide you preferred the older version. Or a game you don't want lose progress in or revert to an old "save".
3) After backing up bloatware, is it then safe to remove and delete?
Click to expand...
Click to collapse
Depends on the bloat. Some apps by AT&T or LG might seem unnecessary or unwanted, but actually are necessary and can cause crashes or force closes ("unfortunately XXXXX process has stopped"). Always back them up first, and remove them one at a time. It's better to freeze them first, then delete after testing. Personally, I don't delete bloat, just freeze it.
4) Schedules, should I be enabling either option?
Click to expand...
Click to collapse
Both, if you want to schedule period backups rather than just doing them youself. Again, your discretion .
5) Main Menu, whats the most important actions to take here?
Click to expand...
Click to collapse
Batch actions and Preferences (where to store them) are all you really should be messing with now. At least until you learn more.
SuperSu
1) Seems fairly straight forward, what are "logs" and do I need to pay attention to them?
Click to expand...
Click to collapse
The logs keep track of what was granted SU access and when. Not really necessary.
2) Settings, is there any options I need to change, take advantage of? Anything I should avoid tampering with?
Click to expand...
Click to collapse
PIN code is your choice. If you're the only one that ever uses your phone, it's not really necessary, but if if you let others use it frequently(for games, or to browse or log into Facebook), you might want to use a PIN so they don't simply hit "grant" whenever SuperSU requests rights. I use "prompt" as the default action, so I know what needs to access the system. For example, some apps that don't require root (like Clean Master) have additional functions if you are rooted, and this might not be clear in the description in Play. That way you know, and you won't accidentally screw something up. Also, malicious apps that have no business with root access can be identified and blocked.
Misc Questions
1) When system updates come out, will this cause me to lose Root access, if so why and how do I avoid that?
Click to expand...
Click to collapse
You can sometimes (usually?) lose root access after an update, but it's usually possibly simply to re-root with the same method. If not, it's best to wait to do the update until others can confirm/deny. SuperSU has a "survival mode" that can try to keep root during an update, but again, it's best to wait for confirmation by others.
2) Is there any prevenitive measures that I need to take to protect my device against any crashes, bricking, or any other general screw ups a newbie might cause with Root access?
3) Also, how do I not destroy my device while learning to take advantage of Root access?
Click to expand...
Click to collapse
Read, ask, and learn. It's easy to grow confident and think you're more clever than you really are and really screw something up (I know from experience). If you look at the first couple pages of general Q&A/Help forums, you'll see lots of people who did stupid stuff and now have bootloops and crashes and bricks. Do lots of searches, here, on google, and youtube. You can often find guides for what you're wanting to do.
4) In addition to what I have already installed, is there any other must have apps for the Rooted user?
Click to expand...
Click to collapse
AdAway or other ad blocker. Not only does it block ads in your browsers, it blocks Google ads in free apps. Apart from being cleaner and more convenient, since ads don't get loaded, pages load faster and you consume less data.
BetterBatteryStats gives you much more info on what's draining your battery than the stock Android function.
Some sort of root browser/explorer is essential. You can use it to completely delete folders/data that got left behind even after an app is deleted (which can sometimes cure Google Play Store errors), among other things.
I personally like ROM Toolbox Pro. It doesn't really do anything special, just packs a ton of utilities that you can get elsewhere into a single app.
SQLite editor is necessary to do some things, but you'd better make sure you know what you're doing before doing anything with it.
WiFi Tether Router might be able to bypass AT&T's tether app. Changing some settings with SQLite might be necessary. You'd have to research this for your device.
Those are the root apps I use, as well as Xposed and assorted modules to do theming or other functionality tweaks. Xposed is quite powerful, and you should familiarize yourself with what the multitude of different modules can do. The possibilities are seemingly endless, as developers come up with no mods every day to do new things that nobody else has done yet (or ported other mods to work with other devices).
I appreciate any & all help, thanks alot in advance!
Click to expand...
Click to collapse
Good luck and have fun!
Planterz said:
I'll answer what I can, as best I can.
Make sure you have BusyBox installed as well.
It's best to change one setting at a time. It's tedious, especially if you have to reboot after changes, but if something goes awry, it's much easier to track down the conflict or bug, especially if you're using multiple modules.
There's a definite learning curve with TB. I'm not sure why some apps might not back up. It could be because they're core components of the OS and are write protected.
When talking about batch backups, "enough" is at your discretion. No harm in doing them periodically, especially if you install a bunch of new apps. Backing up individual apps is good to do before updating them, in case you decide you preferred the older version. Or a game you don't want lose progress in or revert to an old "save".
Depends on the bloat. Some apps by AT&T or LG might seem unnecessary or unwanted, but actually are necessary and can cause crashes or force closes ("unfortunately XXXXX process has stopped"). Always back them up first, and remove them one at a time. It's better to freeze them first, then delete after testing. Personally, I don't delete bloat, just freeze it.
Both, if you want to schedule period backups rather than just doing them youself. Again, your discretion .
Batch actions and Preferences (where to store them) are all you really should be messing with now. At least until you learn more.
The logs keep track of what was granted SU access and when. Not really necessary.
PIN code is your choice. If you're the only one that ever uses your phone, it's not really necessary, but if if you let others use it frequently(for games, or to browse or log into Facebook), you might want to use a PIN so they don't simply hit "grant" whenever SuperSU requests rights. I use "prompt" as the default action, so I know what needs to access the system. For example, some apps that don't require root (like Clean Master) have additional functions if you are rooted, and this might not be clear in the description in Play. That way you know, and you won't accidentally screw something up. Also, malicious apps that have no business with root access can be identified and blocked.
You can sometimes (usually?) lose root access after an update, but it's usually possibly simply to re-root with the same method. If not, it's best to wait to do the update until others can confirm/deny. SuperSU has a "survival mode" that can try to keep root during an update, but again, it's best to wait for confirmation by others.
Read, ask, and learn. It's easy to grow confident and think you're more clever than you really are and really screw something up (I know from experience). If you look at the first couple pages of general Q&A/Help forums, you'll see lots of people who did stupid stuff and now have bootloops and crashes and bricks. Do lots of searches, here, on google, and youtube. You can often find guides for what you're wanting to do.
AdAway or other ad blocker. Not only does it block ads in your browsers, it blocks Google ads in free apps. Apart from being cleaner and more convenient, since ads don't get loaded, pages load faster and you consume less data.
BetterBatteryStats gives you much more info on what's draining your battery than the stock Android function.
Some sort of root browser/explorer is essential. You can use it to completely delete folders/data that got left behind even after an app is deleted (which can sometimes cure Google Play Store errors), among other things.
I personally like ROM Toolbox Pro. It doesn't really do anything special, just packs a ton of utilities that you can get elsewhere into a single app.
SQLite editor is necessary to do some things, but you'd better make sure you know what you're doing before doing anything with it.
WiFi Tether Router might be able to bypass AT&T's tether app. Changing some settings with SQLite might be necessary. You'd have to research this for your device.
Those are the root apps I use, as well as Xposed and assorted modules to do theming or other functionality tweaks. Xposed is quite powerful, and you should familiarize yourself with what the multitude of different modules can do. The possibilities are seemingly endless, as developers come up with no mods every day to do new things that nobody else has done yet (or ported other mods to work with other devices).
Good luck and have fun!
Click to expand...
Click to collapse
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Again, appreciate the feedback.
Vic098 said:
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Click to expand...
Click to collapse
http://d-h.st/BZs
If you haven't done so already, you'll have to go into your settings and check the box to allow app installation from unknown sources. Then just go to that link on your device, download the .apk, then install. Go to a site with a heavy amount of ads like phonearena.com (Verizon ads up the wazoo) and see how long it takes to load. Then reboot, and load the app. It'll update sources, and it'll be good to go. Go back to that website and marvel at how quickly it loads without the ads.
Vic098 said:
Thanks for the detailed response. Just a follow up, when googling AdAway, I see some long threads and what I think are different versions, is there a link, or a place that I can find the latest (and safe??) version to download?
Again, appreciate the feedback.
Click to expand...
Click to collapse
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Radigen said:
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Click to expand...
Click to collapse
Gotchya.
Planterz said:
If you haven't done so already, you'll have to go into your settings and check the box to allow app installation from unknown sources. Then just go to that link on your device, download the .apk, then install.
Click to expand...
Click to collapse
The link downloads a file called mobogenie. Is that correct?
Vic098 said:
The link downloads a file called mobogenie. Is that correct?
Click to expand...
Click to collapse
No. I don't know what that is, and I can't recreate whatever you did to get that. Whatever it is, don't install it.The file to download will match the name in the description. Make sure you're not clicking an ad (oh, the irony).
Try this link instead. https://f-droid.org/repository/browse/?fdid=org.adaway or try downloading on your computer to Dropbox or Drive or whatever cloud storage you use, or just download it to your computer, plug in your phone, copy it to your phone's storage, and run it from there.
Radigen said:
Is this a Xposed Module or some APK off the google market? Because if it's an Xposed Mod then links are direct.
Click to expand...
Click to collapse
Neither. It's not an Xposed module, just a regular app, but it's not available from the Google Play Store because they don't want you blocking your ads, so you have to side load it.
Planterz said:
No. I don't know what that is, and I can't recreate whatever you did to get that. Whatever it is, don't install it.The file to download will match the name in the description. Make sure you're not clicking an ad (oh, the irony).
Try this link instead. https://f-droid.org/repository/browse/?fdid=org.adaway or try downloading on your computer to Dropbox or Drive or whatever cloud storage you use, or just download it to your computer, plug in your phone, copy it to your phone's storage, and run it from there.
Neither. It's not an Xposed module, just a regular app, but it's not available from the Google Play Store because they don't want you blocking your ads, so you have to side load it.
Click to expand...
Click to collapse
Oh alright, thanks then, good thing we're all developers here.