Apology of Java byte/dex code encryption

Preface

An apology is an explanation or defense of actions that may otherwise be misunderstood. There are several sources of misunderstanding concerning Java byte code encryption. An obstacle lies in the narrow perception of protection as a mechanism like a bank safe. The code protection is significant because of its significance in Intellectual Property protection. It cannot be read as an isolated problem because of its roots in the history of software engineering. Another obstacle lies in the unexpected sources of the Java byte-code protection technique. This technique is made possible by facts that seem to have no relevance to programming at first sight.

I’m going to consider whether it is possible to reliably protect Java byte code from plagiarism and re-engineering. There is also a problem with how to protect valuable data such as passwords, URL addresses, personal data of users, etc. I will also give some “examples” in which it is allegedly proved that the protection of Java code is impossible and I will show that these “examples” are untenable. Finally, I will demonstrate that software protection is not the final result but a war between attackers and defenders.

There are a lot of plausible reasoning and myths about the impossibility and uselessness of byte-code encryption, so I decided to write this essay and I think this can have a very significant effect on the programming community. There are many misconceptions about the reliability of Java encryption and other languages, as well as plausible arguments about the impossibility of such protection. Below I will discuss typical errors found in such reasoning.

NOTE. In some cases, examples of my code and reasoning will be incomplete because exhaustive explanations are the intellectual property of BIS Guard & Co. and are not subject to disclosure.