Dump Android Logs Module about drozer HOT 5 CLOSED

We would need the READ_LOGS permission if we were to do this. We could review what permissions Mercury uses but obviously we would like to keep the base Mercury as low-privileged as possible.

Assigning the READ_LOGS permission could also open up the use of more root exploits e.g. Gingerbreak which requires this permission to work, so it could be a good one to add.

@dbradberry what do you think?

from drozer.

I don't think it's a problem to require additional permissions.

If apps are going to keep writing sensitive data into the logs, then we should allow Mercury to gather this information. If that requires extra permissions, fair enough.

We would have to think about how that information would be accessed, however, because log files will be generated asynchronously from everything else; which isn't a mode Mercury supports at the moment.

from drozer.

A simple/hacky solution could be for a module to start a logcat -f loggingfile and background it. Then have code that polls that file every ~2s for diffs and display only the diffs. When the module is stopped then issue a command to kill the backgrounded logcat.

Cheap solution but would probably work quite well...

from drozer.

We can always have this module in Mercury and then have a check at the beginning of the module code to see whether the connected agent holds the READ_LOGS permission.

After all, people should be able to use the Mercury agent with whichever permissions they choose in order to suit their needs

from drozer.

Since JellyBean third party applications can only read their own logs, so this would no longer work.

from drozer.