The art of gaining root on our devices has been a game of cat and mouse nearly since the inception of this operating system we love called Android. Each version of Android and/or an OEM’s own security practices may bring new challenges for the developers to crack in order to allow the end user the freedom to do as they wish with their devices. And with each successful attempt to break in, the authors of the code look for new ways in which to plug the holes. On Halloween 2013, Google introduced their latest iteration of their OS Android 4.4, also known by the moniker “Kit Kat”, and with it implemented several new security improvements. SELinux, first seen in 4.3, moved to an “enforcing” mode rather than the previous “permissive” state. Other changes included support for a different method of encryption in signing keys for apps, handling certificates in a more secure manner and the use of a check code in the kernel to verify the file structure of the system at boot. It is this last mentioned change that could play a major role in the ever escalating battle between the source and the developers in this game.
(Continue Reading @ Android Dissected)
Last edited:
