methods, and it never touches a hard drive in
plaintext form, as it is decrypted on the fly.
Java 9’s introduction of modular JARs has led
to some changes for AxProtector Java. The new
version supports both traditional Java applica-
tions created under Java 7 or 8 and modular
JARs made with Java 9.
AxProtector Graphical User
Interface
AxProtector shows its true potential with its
availability as a command line tool, which
enables full integration into automatic build
processes as part of continuous integration and
continuous delivery. At the same time, a GUI
guides users through the features and functi-
ons and makes AxProtector more comfortable
to use on ISVs’ workstations.
The GUI has been given a new facelift, revitalizing,
in particular, the settings for licensing systems.
Before Universal Firm Codes were introduced
in 2016, software developers needed two firm
codes to combine software and dongle-based
licenses: One for CmDongles and one for CmAct-
Licenses. The Universal Firm Code removes the
need for this distinction, and the new facelift
reflects this in displaying only one firm code
as the standard setting. Developers who still
operate multiple firm codes to maintain compati-
bility are not affected: The option for them needs
only one click of the mouse.
Compatible with WibuKey
their chosen approach to find the right balance
between performance and obsession for security.
The current version of AxProtector is compat-
ible with FIPS mode, a setting that PC users can
configure to ensure that only FIPS-tested imple-
mentations of cryptographic functions in the
.NET framework are allowed. This is a typically
required setting among US official authorities,
making it a relevant feature to remember if
your users belong to this target group.
AxProtector .NET Standard
.NET Standard provides specifications for .NET
APIs that facilitate interoperability and compat-
ibility between different .NET environments. It
makes it easier for ISVs to roll out their appli-
cations across platforms or to migrate from one
platform to another.
The current release brings the launch of another
version – AxProtector .NET Standard – equipped
to protect .NET Standard 2.0 applications like
.NET Core 2.0 or Mono 5.4 applications.
The protections work on the same basis used
with AxProtector .NET: The application is ana-
lyzed and protected by encryption on the
method level. It can only be decrypted and
executed if the correct license is available in a
CodeMeter container.
AxProtector Java
When compiling Java Source Code, the code is
first translated into a unique interim language,
called Java Byte Code. On the target platform
the Java Virtual Machine (JVM) then sees to it
that this code is interpreted and executed. This is
the secret to Java’s platform independence, but it
also adds certain weaknesses from the point of
view of the security of the Java Byte Code.
As with .NET, the Java Byte Code is simple to
decompile and makes reverse engineering less of
a challenge for would-be attackers. AxProtector
Java has the power to stop them in their tracks
by encrypting the code – as its sister implemen-
tations do – and tying it to a specific license. The
code can be encrypted on the level of classes or
CodeMeter Protection Suite supports all Code-
Meter licensing systems currently in the field:
CmActLicenses and CmDongles. CodeMeter
Protection Suite also continues to support
WibuKey, the predecessor of CodeMeter origi-
nally introduced in 1989. This is what Wibu-
Systems means by long-term availability and
lasting compatibility.
Always Evolving, Continuously
Improving
All parts and components of CodeMeter Pro-
tection Suite are in continuous development,
of course, with particular attention to security
and performance. New capabilities like the
ability to have executable code on CmDongles
or the automatic setting of traps are just two
examples of constant evolution. Caching mech-
anisms have been introduced and refined to
improve performance. A committee of experts
is charged with overseeing current and planned
security features to make sure they deliver real
added value and do not impact performance.
For CodeMeter Protection Suite, only the best
and fastest mechanisms make the cut.
13