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

Discovering the objects behind android APIs #1

Open
Fare9 opened this issue Mar 12, 2021 · 1 comment
Open

Discovering the objects behind android APIs #1

Fare9 opened this issue Mar 12, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@Fare9
Copy link
Collaborator

Fare9 commented Mar 12, 2021

For the moment in permissionTracer if we see that onBind returns an android API, we return get None in that case as can be seen in https://github.com/Android-Observatory/PermissionTracer/blob/main/permissionsTracer.py#L437 a good idea it would be to continue the analysis in that case for doing the next:

For example if the program returns only an object of type: android.os.Binder. This could mean that the program returns an empty interface for using it, or it could mean that the object of type android.os.Binder was instantiated before with another type of class (an interface written by the programmer) because Binder class is a base clsas that should be extended.

The method for the analysis should search where the Binder object is initialized and return the possible classes that Binder object could be, so later we can extract all the methods from that class.

@Fare9 Fare9 added the enhancement New feature or request label Mar 12, 2021
@Fare9
Copy link
Collaborator Author

Fare9 commented Mar 25, 2021

I've included some methods for the analysis of Androguard's AST of a method: 8c6077c. I think this needs some work yet, also I've modified the code that included the methods signature int the list.

Example of output:
{ "Lcom/qualcomm/qti/callenhancement/CallEnhancementService;": { "component_type": "Service", "data_provided": {}, "intent-filter_actions": [], "interface": [ { "<init>": { "parameters": [ "Lcom/qualcomm/qti/callenhancement/CallEnhancementService;" ], "return-type": "void" } }, { "canCallRecord": { "parameters": [], "return-type": "boolean" } }, { "getRecordedCallDuration": { "parameters": [], "return-type": "long" } }, { "isCallRecording": { "parameters": [], "return-type": "boolean" } }, { "registerCallRecordStateChanged": { "parameters": [ "Lorg/codeaurora/callenhancement/ICallRecordStateListener;" ], "return-type": "void" } }, { "startRecordingCall": { "parameters": [], "return-type": "void" } }, { "stopRecordingCall": { "parameters": [], "return-type": "void" } }, { "unregisterCallRecordStateChanged": { "parameters": [ "Lorg/codeaurora/callenhancement/ICallRecordStateListener;" ], "return-type": "void" } } ], "protected_apis": {} } }

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

No branches or pull requests

1 participant