Quote:

we can handle several Client versions (each with its own obfuscation) with the very same Server.

Another Quote:

Then, if/when a zero-day bug is encountered in TLS – our obfuscation does provide additional protection even before the attacker can reach the code with that zero-day vulnerability

Quote:

This is all what the-best-available-decompiler was able to do with our obfuscated code

Another Quote:

Performance-wise, we can do A LOT of obfuscation per network tick

Quote:

However, we can (and SHOULD) do MUCH better than that

Another Quote:

With our approach, each and every obfuscation has to be hacked individually..

Quote:

Technically, what we’re looking for here, is any kind of bijection; we’ll use this bijection to convert our data from one representation into another one (and as it is a bijection, we can revert it later).

Another Quote:

As we’re not writing our obf<> classes manually (instead, we have a code generator doing it for us on each build), the sky is the limit to the obfuscations we can generate."<> classes manually (instead, we have a code generator doing it for us on each build), the sky is the limit to the obfuscations we can generate.