Android applications security — part 1, reverse engineering and token storage problems by Adrian Defus

January 29, 2019
(173 views)

There are many ways you can store keys and tokens in your Android applications — directly in the code, inside your database or by using NDK layer. But in terms of security — should you do it at all?

This article will show you the most common ways you can use to store different types of keys and tokens in your Android applications, while proving that none of these methods is good enough ????. The second part will contain more detailed considerations regarding how our application should communicate securely with the server, how to ensure the authentication of both entities, and how the attacker can affect our connection.

Looking inside our applications (reverse engineering)

The applications which we use on our devices are actually properly packed .apk files containing all the data required to operate correctly. If we want to view their content and see what is hidden there, we have to make some necessary preparations. First of all, we need a tool that will let us communicate with the mobile device using our computer — Android Debug Bridge is what we are looking for. Secondly if we want to disassemble our .apk files into separated source code files (.smali classes), Apktool seems to be the perfect....

Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

2 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
© HAKIN9 MEDIA SP. Z O.O. SP. K. 2023
What certifications or qualifications do you hold?
Max. file size: 150 MB.

What level of experience should the ideal candidate have?
What certifications or qualifications are preferred?

Download Free eBook

Step 1 of 4

Name(Required)

We’re committed to your privacy. Hakin9 uses the information you provide to us to contact you about our relevant content, products, and services. You may unsubscribe from these communications at any time. For more information, check out our Privacy Policy.