How we build Android Tamer

For first three releases we experimented with multiple methods and expreiments doesn’t stop this time around also.

This time we wanted to see if we can automated most of the stuff that we do. so we looked at existing processes and we identified that best combination for us could be to use a combination of vagrant and ansible playbooks.

So we first build a basebox of ubuntu 14.04LTS with bare minimums and used that as base box. (Just for the heck of it, but we also customized the username and hostname of the instance since we were anyways modifying stuff.)

After delibrating for a couple of day and based on various internet chatter we decided to shift our base to Debian 8 and hence another base box was created with bare minimum’s but this time using debian 8 as base.

This box was then used to couple with ansible scripts and the final product is what you see now.

Entire Vagrant Ansible configuration is available here

The base box used for all the activities

With more delibration about the future of AndroidTamer we decided to opensource every single bit of whatever we are doing in AndroidTamer project.

All the projects are hosted at Github

Feel free to contribute / curse / raise questions

Do you like what you read, What to share it

Author: Anant Shrivastava

Anant Shrivastava is a Independent Security Consultant and Trainer. He holds various certifications like SANS GWAPT, CEH and RHCE. He has been Speaker / Trainer at various conferences like Nullcon, C0c0n, Clubhack, G0s, Rootconf. He specialize in Web Application Security, and Mobile Security. He is also developers / maintainer of androidtamer (Live ISO for Android work), WP-Filemanager (Wordpress file manager plugin), SVN-Extractor (pentest tool to extract svn details) and more.

One thought on “How we build Android Tamer”

  1. Hi Anant,
    Thank you very much for helping and Android tamer I have completed my assessment on Android application and found 3 risks from owasp mobile top 10

Leave a Reply

Your email address will not be published. Required fields are marked *