Version 2.4.7

Requirement:
================
Microsoft .NET Framework 4.6 (https://www.microsoft.com/en-us/download/details.aspx?id=53345)
WIBU SYSTEMS CodeMeter Runtime (https://www.wibu.com/uk/support/user/downloads-user-software.html)

Important changes:
====================
Token support is implemented on new installations via the digitronic Token Engine.
This requires the digitronic Token Engine version 1.1 (http://www.digitronic.net/download/TokenEngineSetup.zip)
Please note the instructions in the ReadMe1st.txt of the TokenEngine. Users who use HiCrypt with MARX-Token and SafeSign or Cryptovision have to set up the token engine accordingly.
When updating HiCrypt, the previous setting is retained.

Token usage (migration)
Due to the changeover to the token engine, there are some things to consider when the HiCrypt token support was previously used with the CSP from Microsoft or a third-party vendor.

If SafeSign (AET Middleware) was previously used:
In this case, there are no special considerations on the usage of old tokens if the key pairs stored on the token are not changed by hand.
Tokens that are prepared via the token engine can not be used with the setting CSP.

If Cryptovision was previously used:
Tokens that have been prepared with the Cryptovision setting can be used with the token engine.
If HiCrypt users have already been linked to the token with the cryptovision configuration, a compatibility mode must be activated in HiCrypt if the token engine is to be used in the future.
To do so, a REG_SZ with the name TokenEngineCompatibilityMode and the value Cryptovision must be created in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\digitronic\HiCrypt\Token\Parameters key.

If the old version of the token engine and DESFire were previously used:
It is important to note that token, which are prepared with the new version, can not be used with the old version.

Known issues:
=============
none