2.1. System Requirements¶
2.1.1. Supported Operating Systems¶
- Windows 8, 10, 2012 Server, 2012R2 Server, 2016 Server, 2019 Server. Full support on X86 and X86_64 architectures.
- Red Hat Enterprise Linux 6, 7 on X86_64. On request, we provide builds for older versions (RHEL 5) or different architectures (x86, POWER8, S390x). Make sure the “libffi” package is installed.
- Amazon Linux AMI 2018.03 on X86_64, using the RHEL 7 package.
- Amazon Linux 2 AWS on X86_64.
- SUSE Linux Enterprise Server 11 SP4 (with or without the Security Module), and 12 SP3 on X86_64.
- Ubuntu Server 14.04 LTS, 16.04 LTS, 18.04 LTS on X86_64.
- Ubuntu Server 16.04 LTS on ARM64 (ARMv8-A/AArch64).
- Debian Linux 8 on X86_64. Contact us if you need support for a newer Debian Linux version and/or another hardware platform.
- Alpine Linux 3.7 on X86_64. Contact us if you need support for a newer Alpine Linux version and/or another hardware platform.
- IBM AIX 7.1 or newer on POWER7 and newer systems. The OpenSSL 1.0.2 libraries from IBM are required, and can be obtained free of cost from the AIX Web Download Pack Programs web page. This version is built against OpenSSL libraries version 1.0.2k on AIX 7.1 with Technology Level 3. Contact us if you are using an older AIX version and/or POWER CPU.
- Oracle/Sun Solaris 10 for x86_64 and SPARC. Solaris 10 packages for SPARC are provided in 32bit only. On Solaris 10, the OpenSSL 1.0.2 libraries from Oracle are required, and can be obtained through Oracle Support Patches. On Solaris 10, this version is built against OpenSSL libraries version 1.0.2n from Oracle patches 151912-11/151913-1 on Solaris 10 U11 systems.
- Apple OS X 10.8 on x86_64. Newer versions should also work, but these systems are not included in our automated test suite. If you encounter problems on your systems, please contact us.
- Apple macOS Sierra 10.12 on x86_64 with OpenSSL 1.0.2 libraries provided by the Homebrew community. macOS 10.11, 10.13 or newer should also work, but these systems are not included in our automated test suite. If you encounter problems on your systems, please contact us. This version is built against OpenSSL libraries version 1.0.2o.
- HP-UX 11iv3 on Itanium2 is supported with limited functionalities. See details in the known issues page. The OpenSSL 1.0.2 libraries from HP’s Software Depot for HP-UX 11i are required. This version is built against OpenSSL libraries version 1.0.2k.
Virtual environments and virtual machines are supported for all platforms, including: VMWare ESX, VirtualBox, OpenVZ, Docker, WPAR, vWPAR, zones, etc.
SFTPPlus does not include cluster-aware logic, but it provides generic functionalities for implementing clustering.
We have customers deploying SFTPPlus resilience configuration on MSCS, Red Hat Linux, and IBM AIX clusters. To read more about our approach to fault tolerance and zero redundancy deployments please see our guide.
On MSCS, SFTPPlus can be deployed as a Generic Service Resource or a Generic Script Resource.
2.1.2. Software Requirements¶
On Microsoft Windows, the OpenSSL library is distributed together with the installation package and there are no 3rd party dependencies.
On Unix/Linux operating systems, the product uses the OpenSSL libraries available on the OS. As such, we recommend that a recent version of the OpenSSL library is installed to benefit from the latest security fixes.
On MacOS systems, you will need to install the OpenSSL 1.0.2 libraries provided by the Homebrew community.
2.1.3. Hardware Requirements¶
The server will run on any CPU released in the last decade.
Since many of the encryption / decryption operations are CPU-intensive operations, using a modern system designed for server usage is recommended.
Between 30 - 100 MB of RAM, depending on CPU architecture.
Memory usage will increase with the number of concurrent connections. No more than 1 MB will be used for a new connection.
Installation size: 200 MB.
The server will try to use all available network bandwidth. This is normal for Ethernet/IP networks.
The available bandwidth will be shared by all connections.
Many of the cryptographic algorithms require a low network latency and a network delay not larger than 60 seconds.