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

Permissions taken into consideration for risk score computation #50

Open
GoogleCodeExporter opened this issue Mar 20, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. _a = AndroguardS(inputfile.apk)
   perm_set_1 = _a.get_analysis().get_permissions([]) 
2. a = apk.APK(inputfile.apk, raw)
   perm_set_2 = a.get_details_permissions()

perm_set_1 != perm_set_2 !

From my experience with malware apks, the first set is the one that is 
effectively used by the code, or am I wrong? 

But the risk module takes into consideration the 2nd set while computing the 
risk score (or am I wrong again?)


I'm using:

androrisk.py --version
Androrisk version 1.0

on Linux version 3.3.5-2.fc16.i686.PAE (mockbuild@x86-07.phx2.fedoraproject.org)


Of course Anthony, I realize that this might be the behaviour that you desire 
for androguard, I just wanted to be sure that you're aware... :)

Best Regards,
Madalina

Original issue reported on code.google.com by madalina...@telecomitalia.it on 4 Jun 2012 at 9:48

@GoogleCodeExporter
Copy link
Author

Original comment by anthony....@gmail.com on 2 Jul 2012 at 3:59

  • Changed state: Accepted

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

No branches or pull requests

1 participant