Upgrading OpenSSL on Linux for Connect 3.7.1


In order to run Connect 3.7.1 and above on Linux, your system must have OpenSSL 1.0.2g or newer. If you have an older version of OpenSSL, you will see the following message when trying to install Connect 3.7.1:

OpenSSL is too old to support Aspera Connect. Please upgrade to version 1.0.2g or newer before trying to install Aspera Connect. 

If you have an older OpenSSL version, you will need to upgrade to the latest (1.0.2g and above).


1. Make sure you are logged in as root and download the latest version of OpenSSL:

wget https://www.openssl.org/source/openssl-1.0.2-latest.tar.gz

2. Untar the package

tar -zxf openssl-1.0.2-latest.tar.gz

3. If you do not have C compilation tools gcc and/or make, install them through your package manager

# yum groupinstall 'Development Tools'

# apt-get install build-essential

4. Run the following commands in the openssl-1.0.2X directory (where X is the latest letter version you downloaded)

# cd openssl-1.0.2X
# ./config shared -fPIC -dPIC
# make depend
# make
# make install

5. Add OpenSSL to your path with the following command

# ln -s /usr/local/ssl/bin/openssl /usr/bin/

If you receive an error that the file /usr/bin/openssl already exists, move the existing file to a directory of your choice and retry the command above.

6. Replace the libssl.so.1.0.0 and libcrypto.so.1.0.0 files from your system's shared library folder

The location of your system's shared library folder will differ based on your Linux distribution. Below are the usual locations:

  • CentOS/RHEL: /usr/lib64
  • Ubuntu: /lib/x86_64-linux-gnu
  • Debian: /usr/lib/x86_64-linux-gnu

Copy the two files from the /usr/local/ssl/lib path as below:

# cp /usr/local/ssl/lib/libssl.so.1.0.0 shared_library_directory/
# cp /usr/local/ssl/lib/libcrypto.so.1.0.0 shared_library_directory/

If your shared library directory differs from those given above, you can determine the location by looking at the Connect logs at /home/user/.aspera/connexr/var/log/aspera-connect.log.

Look for a line that contains the libssl.so.1.0.0 file:

2017-02-13 16:19:27 [203-48cf6780] ERR  4:0x00007fea31ddfc39 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 SSL_free+73

This tells you that your shared library directory is /usr/lib/x86_64-linux-gnu, and that's where the two files will need to be copied to.

7. Link the new OpenSSL libraries

In the shared library directory, run the following commands:

# ln -fs libssl.so.1.0.0 libssl.so
# ln -fs libssl.so.1.0.0 libssl.so.10 
# ln -fs  libcrypto.so.1.0.0 libcrypto.so
# ln -fs libcrypto.so.1.0.0 libcrypto.so.10
Have more questions? Submit a request


  • Avatar
    Khai Lam

    Based on notes about nginx, where the product was compiled with openssl 1.0.2 libraries linked in, couldn't the aspera-connect plugin be compiled with the needed openssl libraries as well (maybe drop it into /usr/local/lib/ or /usr/local/src/)? The above proposed solution potentially causes problems with other openssl-dependent applications like ssh and firefox and is thus far from ideal.

  • Avatar
    Khai Lam

    Okay, confirmed. The above instructions kills sshd. After copying in the library files, you need to run `ldconfig` or `service sshd restart` will barf.

Please sign in to leave a comment.
Powered by Zendesk