IBM Aspera Shares 1.9.2

  • Product Release: June 15, 2015
  • Release Notes Updated: June 15, 2015


This release of IBM Aspera Shares 1.9.2 for Linux (64-bit) includes support for the IBM Aspera Connect Browser Plug-In 3.6.0.


#12883 - When searching (browsing) recursively, the sort parameter is ignored.

#14532 - The transfer rate and encryption settings in Shares can be circumvented by users if they manually change the FASP URL before submitting. Workaround: In order to enforce the settings, set the desired values in the aspera.conf file on the node.

#15396 - The transfer fails when you attempt to download special files like symlinks, block and character device files, socket, and so on.

#18579 - If you perform a search for remote groups that start with backslash (\) or asterisk (*), Shares cannot find them.

#25041 - Due to changes made by Google to its mail server’s handling of images in email (Dec 2013), the Aspera Shares logo is not displayed in email notifications. Customers not using a gmail server do not encounter this problem.

#27187 - If the node is set to use Encryption-at-Rest (EAR) but Shares is not set to use EAR, downloading content that is a mix of encrypted files, unencrypted files, and files encrypted with a different password does not prompt the user for a password.

#27188 - If Shares is set to use EAR, downloading a file that was not encrypted will ask for a passphrase.

#27218 - If Shares is set to use EAR, HTTP fallback download of unencrypted content fails with numerous errors. Common errors include: "Insufficient permissions", "Server refused request", and "Connection Lost" errors.

#27228 - If the node is set to use EAR, downloading multiple encrypted files/folders or a single folder with encrypted files does not prompt for a password.

#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to log in. Workaround: Turn off "Extended Protection" in ADFS SAML IdP. Doing so at first produces random ADFS SAML user login failures with an "Invalid SAML response" error and infinite redirects upon login; but in the longer term, this does fix the problem.

#28359 - SSLv3 is disabled by default to address a security threat. If you are using an older version of Aspera Drive (pre-1.2.0), upgrade Drive to the latest version.

#29530 - (Linux Only) Stats-collector displays an error when working with nodes that are configured for tlsv1 or tlsv1.1. Linux Shares works with nodes that are configured with tlsv1.2 or sslv3 only."

#29543 - (Windows Only) Shares displays an SSL error when adding a node with ssl_protocol set to tlsv1.1 or tlsv1.2.

#29580 - If a share's name has a forward slash ("/") in it, this share cannot sync with Aspera Drive. The sync action fails, with a "Path not found" error. Transfers between these shares using the API also fail with a "Path not found" error.


IBM Aspera Enterprise/Connect Server: A licensed version of 3.3+.
Note: The share-to-share transfers feature should be used with special build 3.4.32 or with 3.4.5+.

Linux 64-bit: RHEL/CentOS 6 and 7

Browsers: Internet Explorer 8+, Firefox 27+, Safari 6+, Google Chrome 32+


Linux 64-bit: aspera-shares-
md5: ef6ea22e1dffacd0f39ba4d49635eadc
sha1: a9a6473288d6292d08f8c7d96cb6150098652efc


For on-line support resources for Aspera products, including raising new support tickets, please visit theAspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk