Is there a file name wrong in QuickStart.md ? about libradar HOT 6 CLOSED

1. API dict and Job_dispatching is just for professional use（That means you want to extract features from large data set of APKs by yourself.） If you just want to exam several apks' libraries, just use one python script: "libradar.py"

2. Even if you want to extract millions of apks to extract features by yourself, you can skip api_dictionary.py.

3. My Operating System is Mac OS X. Any Unix-like OS can use LibRadar. I haven't check this tool on Windows. I guess it could works the same, until you move out "rm" & "eject" because they are instructions for Linux shell. Just remove the code line and try again.

from libradar.

I moved out "rm" & "eject" and ran job_dispatching.py again, the results are as follows:

C:\Users\Administrator>python d:\LibRadar\LibRadar\job_dispatching.py
2017-05-23 10:01:45,394: INFO     Pool created
2017-05-23 10:01:45,403: INFO     Waiting for all sub-processes done.
2017-05-23 10:01:45,608: INFO     Process 00 is running
2017-05-23 10:01:45,627: INFO     Process 01 is running
2017-05-23 10:01:45,645: INFO     Process 02 is running
2017-05-23 10:01:45,671: INFO     Process 03 is running
2017-05-23 10:05:35,523: INFO     Process 00 returns
2017-05-23 10:05:35,707: INFO     Process 04 is running
2017-05-23 10:05:36,079: INFO     Process 03 returns
2017-05-23 10:05:36,250: INFO     Process 05 is running
2017-05-23 10:05:49,125: INFO     Process 01 returns
2017-05-23 10:05:49,341: INFO     Process 06 is running
2017-05-23 10:05:53,923: INFO     Process 02 returns
2017-05-23 10:05:54,101: INFO     Process 07 is running
2017-05-23 10:06:05,709: INFO     Process 04 returns
2017-05-23 10:06:06,252: INFO     Process 05 returns
2017-05-23 10:06:19,342: INFO     Process 06 returns
2017-05-23 10:06:24,102: INFO     Process 07 returns
2017-05-23 10:06:24,213: CRITICAL All sub-processes done.

I still don‘t know which folder the analysis results are put in.(I really want to analyse about 200 thousand apks.I tied to just use libradar.py for 100 apks,it takes about 7 seconds per apk, so it will spend too much time to analyse all apks).Thanks for your help.

from libradar.

job_dispatching.py is not used for boosting libradar.py. It is used for feature training.

If you want to use libradar fastly, you can write a script to execute libradar.py on several processes.

from libradar.

Oh,that's it.Thank you very much!

from libradar.

until you move out "rm" & "eject" because they are instructions for Linux shell

I don't know what LibRadar used eject (which is to eject compact-disks/dvds and the like) – but instead of rm, there are the platform independent os.unlink (to remove a file) or os.rmdir / os.removedirs (to remove a directory / recursively). But I guess there's a reason you didn't use any of those, @pkumza (didn't check thoroughly; it's the loop cleaning up the smali stuff I guess).

from libradar.

Eject is just a trick for notice you works have been done (It eject your cd-rom).

Use os module instead of rm is a good practice for compatibility. Yes. But I don't want to waste much time for it as just few people will use job_dispatching.py for training stage. To clear that, I'd like just rm -rf harshly.

from libradar.