OpenSSL requirements

The following Synergy/DE features require OpenSSL. Before installing OpenSSL, consult the documentation pertaining to the feature you plan to use for additional details and information on any environment variables or paths you need to set.

• Synergy HTTP document transport API to send and receive documents via HTTPS. See Synergy HTTP Document Transport API.
• Data encryption at the application level. See Data encryption.
• Client/server encryption with xfServer or xfServerPlus. For xfServer, see Using client/server encryption. For xfServerPlus, see Using xfServerPlus encryption.
• Data packet encryption with SQL OpenNet. See Using data packet encryption for SQL OpenNet.
• PostgreSQL access via SQL Connection. See PostgreSQL notes.

Windows

Synergy/DE 10.3.3 supports OpenSSL version 1.0.*.

Go to https://slproweb.com/products/Win32OpenSSL.html and download the “light” version that matches the bitness of your system. When unpacked, the download will include two libraries, libeay32.dll and ssleay32.dll, along with a number of other files. (These library files are named with “32” for both the 32-bit and the 64-bit versions of OpenSSL.)

For both 32-bit and 64-bit traditional Synergy, you must copy the libraries to the corresponding 32-bit or 64-bit SynergyDE\dbl\bin directory.

For SQL OpenNet, you must also copy the libraries to the corresponding 32-bit or 64-bit SynergyDE\connect directory.

For Synergy .NET, if DBLDIR is set, Synergy will look in the \bin directory under the DBLDIR directory for the OpenSSL DLLs. If DBLDIR is not set or the libraries are not found there, the default DLL lookup path for Windows is used (PATH, then current directory). We do not recommend putting OpenSSL DLLs in the path, as there may be more than one instance of the OpenSSL DLL in the path and you can't have both 32- and 64-bit. Instead, if DBLDIR is not set, we recommend putting the OpenSSL DLLs in the same directory as your assembly and adding a manifest to ensure loading of the correct DLL.

For ClickOnce deployment, OpenSSL must already be installed on the target machine; you cannot install the OpenSSL libraries via ClickOnce.

UNIX

For Synergy/DE 10.3.3, you should use the version of OpenSSL that comes from the vendor and is specific to your UNIX platform and version. The OpenSSL shared libraries required by Synergy/DE are libcrypto.so.#.#.# and libssl.so.#.#.#, where #.#.# is the version number, e.g., 1.0.1.

• For HP-UX, use version 1.0.*x.
• For IBM AIX, use the version installed with the operating system. It should be at least 1.0.*x.
• For Linux, use the version installed with the operating system. It should be at least 1.0.*x.
• For Solaris 11, install the latest version 1.0.*x from Oracle. For Solaris 10, see Synergex KB article 100001979 for instructions on updating to 1.0.*x.

Synergy/DE features that use OpenSSL will display an error if the correct version cannot be found. If you are in doubt as to whether you have the correct version for the features you want to use, run one of the following commands:

• For data encryption, and client/server encryption with xfServer or xfServerPlus:

ldd $DBLDIR/bin/synssllib.so 

• For HTTPS encryption:

ldd $DBLDIR/bin/httpslib.so

OpenVMS

Synergy/DE 10.3.3 supports HPE SSL1 version 1.0-2C and higher (which is based on OpenSSL 1.0.2 C). SSL1 requires HP OpenVMS 8.4 or higher or VSI OpenVMS 8.4-2L or higher. On HP OpenVMS 8.4 and VSI OpenVMS 8.4-2L, the runtime support files are SYNSSLLIB.EXE and HTTPSLIB.EXE.

Connectivity Series supports HPE SSL1 version 1.0-2C and higher. The runtime support file is VTXSSL.EXE.

For OpenVMS, you must use the operating system-supplied libraries, which are available from VMS Sofware Inc. Contact VSI for more information, https://vmssoftware.com.