Starting with SecureAnyBox 5.7.1, the installation script automatically detects whether your Linux distribution uses the systemd init system. Based on this detection, it configures the appropriate startup mechanism.

1. systemd Support #

If systemd is available, the installer will:

• use systemd as the service manager,
• create and register a service unit named secureanybox5.service for automatic startup,
• back up any existing init.d script created by earlier versions of the installer.

You can control the service using standard systemctl commands:

systemctl start secureanybox5.service

systemctl stop secureanybox5.service

systemctl restart secureanybox5.service

2. init.d Support (Non-systemd Distributions) #

If your distribution does not support systemd, the installer falls back to the traditional init.d system. In this case, Linux Standard Base (LSB) must be installed to enable automatic startup registration.

The installer checks for LSB and notifies you if it is missing. Installation procedures vary by distribution and are listed later in this document.

3. Java Runtime Requirements #

SecureAnyBox5 supports only the following JVMs:

• Oracle Java, or
• Eclipse Temurin (Adoptium).

A tested Eclipse Temurin JVM distribution is included in every installation package. You may choose to:

• use the bundled Temurin JVM,
• install your own Oracle/Temurin JVM manually, or
• point the installer to an already-existing Java installation.

Important:
Some JVM distributions (especially Oracle) restrict cryptographic policies by default. Without the Unlimited Strength policies installed, passwords longer than 7 characters cannot be used. (Refer to Oracle’s documentation for details.)

4. Installation Path #

The default installation directory is:

/opt/tdp/secureanybox

You may change this path according to your requirements.

5. Selecting IP Address and Port #

During installation, you must specify:

• an IP address, and
• a port.

These values can be modified later in the management console. We recommend using the default port initially to avoid conflicts with other running services.

If a port conflict is detected later, the system will automatically revert to the last known good configuration.

6. Enabling SSL (HTTPS) #

It is highly recommended to switch to SSL (HTTPS) as soon as possible.

You can:

• generate a self-signed certificate within SecureAnyBox5, or
• import an existing certificate with a private key (typically in PKCS12 format).

Note:
Interfaces in SecureAnyBox5 are virtualized. You must configure both the IP address and the URL; otherwise, the system cannot accept incoming requests.

7. Upgrading SecureAnyBox5 #

To upgrade SecureAnyBox5, use the same installation script as for a fresh installation.
Please ensure that:

• the same installation path is used, and
• when prompted, choose NOT to overwrite the configuration file.

StepUp from previous SecureAnyBox:

Because SecureAnyBox5 uses a different licensing model, you must review your required license before upgrading from version 4.x. Administrators can determine the necessary license type and number using the Utilization (SecureAnyBox5) report available from version 4.31.0 onward, or by contacting your vendor.

Installing Linux Standard Base (LSB) #

LSB is required only when using the legacy init.d system (i.e., on non-systemd distributions).

RPM-Based Distributions (SUSE / RedHat / CentOS) #

sudo yum install redhat-lsb-core

Deb-Based Distributions (Ubuntu / Debian) #

sudo apt-get install lsb-core

SUSE Linux Enterprise Server 15 SP4 and OES 2023 #

1. Download the package:

wget https://download.opensuse.org/repositories/openSUSE:/Factory/standard/noarch/lsb-release-3.3-1.3.noarch.rpm

2 Install it:

sudo rpm -ihv lsb-release-3.3-1.3.noarch.rpm –nodeps

insserv-compat Requirement (OpenSUSE and Some Others) #

Some distributions require insserv-compat to properly enable init scripts:

sudo zypper install insserv-compat

Manual Registration of init.d Script #

If LSB cannot be installed or is not available for your distribution, you can manually register the startup script. The installer always creates it at:

/etc/init.d/