Private Key Protection

Parent Previous Next

Private Key Protection.

If you have purchased a multi-user license type, many authorized users may access the generated files "LicenseID.txt" and "PrivateKey.txt" as stated by the End User License Agreement (EULA).

However, in a multiuser environment it may be difficult to keep the private keys safe and secure at all times.

Password Protection.

Due to this security concern, it may be advisable to protect the private keys with a password, which are known only by the relevant developers.

The IDE contains a wizard located in the License Menu to assign a password to the private keys.

Once a password has been assigned, the private keys are encrypted and can't be used without this password.


Always keep a backup of the original unprotected file "PrivateKey.txt" in a safe and secure manner. If you forget the password for a protected version of the file, you will need to use the original unprotected file to create a new protected version. A forgotten password can't be reconstructed and is not saved anywhere.

Using a Protected Key.

Whenever a private key is needed by the compiler, it will prompt the developer to enter the password before proceeding. This can't be bypassed.

Once a password is provided, the IDE will remember it in memory and try to use it as a qualified guess the next time a password is required by the compiler, to avoid having the developer enter the password numerous times within the same session.