Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permission for instrumented android socket #4

Open
ftc opened this issue Oct 11, 2016 · 1 comment
Open

Permission for instrumented android socket #4

ftc opened this issue Oct 11, 2016 · 1 comment

Comments

@ftc
Copy link
Member

ftc commented Oct 11, 2016

If the instrumented app does not have the permission for network communications then the instrumentation will not work. Currently we are adding this manually but it would be nice to do it automatically.

@smover
Copy link
Contributor

smover commented Oct 12, 2016

It seems in another sable related project (soot-inflow-android, used by flowdroid) they parse the manifest https://github.com/secure-software-engineering/soot-infoflow-android/blob/develop/src/soot/jimple/infoflow/android/manifest/ProcessManifest.java

They have a method addPermission there.

The project is: https://github.com/secure-software-engineering/soot-infoflow-android

From the flowdroid page:

    soot-infoflow – This contains a generic taint analysis.
    soot-infoflow-android – This models the Android lifecycle etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants