Android Parser Contactos

[AburtoArielPM]

Hello everyone. I made a parser that takes contacts from two databases extracted from an android device, based on other IPED parsers.

[lfcnassif]

Thank you very much @AburtoArielPM!

If no one else takes a look at this before me, I'll try to review after other older PRs sent before.

[AburtoArielPM]

Android Parser Contactos: Ok, after publishing the "Android Parser Contacts", I continued working on it, being able to improve the following:

• Unify in the same Parser the two queried databases.
• Not to touch the "Localization" files.
• That the information is presented in the "Preview" window of IPED.
• That if there are empty fields they are not loaded to the file.
• Do not add new Sub-Categories in the "CategoriesConfig" file, that is, use the ones that were already available.

Also, I clarify and give credit to the ALEAPP code from which I took the query to the Android database.
Any improvement, I am attentive to your comments, corrections, and so on. Always hoping it will be helpful!

[lfcnassif]

Thank you very much @AburtoArielPM for your work on this!

But one old idea we must discuss with other project developers is if it wouldn't be better to integrate ALeapp tool directly as suggested in #43. I see some advantages using this approach:

• Get all ALeapp supported artifacts and results with the same (non trivial) code;
• Less maintenance effort from our side since Android artifact parsing will be delegated to ALeapp;

And some disadvantages:

• More java/python mixed code, what can be harder to debug;
• More python code, what can result in processing bottlenecks because of the infamous python Global Interpreter Lock;