Release Notes: IBM Aspera Shares 1.9.12

Product Release: March 14, 2018
Release Notes Updated: March 16, 2018

This maintenance release of IBM Aspera Shares for Windows and Linux provides an upgraded SAML gem to address a SAML vulnerability. These release notes list system requirements and image information.


  • SAML gem is now at version 1.7.0 to address a vulnerability.


IBM Aspera Enterprise Server licensed with Connect Server 3.6.0-3.8.0.
IBM Aspera Connect 3.6.1-3.7.4
Windows 64-bit: 2008 R2, 2012 R2, 2016
.NET Framework 2.0, 3.0, 3.5, or 4.0.
Linux 64-bit: RedHat 6-7, CentOS 6-7, Fedora 16-20, Ubuntu 12-14, Debian 6-7, SLES 11-12 
Kernel 2.4 or higher and libc version GLIB 2.3.4-2.40.
Browsers: Internet Explorer 9-11, Firefox 27-58, Safari 6-11.2, Google Chrome 40-65

(Shares users can successfully access Shares from any of these browsers on any OS, as long as the browser and OS are also supported by IBM Aspera Connect.)


Linux 64-bit (rpm): aspera-shares-
md5: 51243bf504d6708ed96765c255f2e639
sha1: 6ebd7732306163f4a4fe6ff3a122f3ab7af8b19c
Windows: AsperaShares-
md5: c31b29bbe25b2cb323228aded4c84da7
sha1: d404bfbf1176ef584aa980845bb101eb8514f7f5


#36123 - Transfers with Shares that are initiated from an Aspera desktop application GUI have float values instead of integer values for 'user_id' and 'share_id' in tags.

#29575 - Shares that have names that include a forward slash ("/") cannot synchronize with Aspera Drive or transfer to other shares; both fail with a "Path not found" error.

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

#28143 - The Disabled checkbox (Admin > Directories > SAML > Security) for a SAML directory is not functional.

#27371 - ADFS SAML users running Chrome 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.

#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.

#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.

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

#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.

#26342 - When a local node is added to shares twice, one with host and one with host localhost, the node with host displays a stats collector error.

#25139 - For Shares servers that are installed on Windows, performing a share-to-share drag-and-drop transfer from a share that does not support share-to-share will trigger an "Internal error".

#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.

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

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

#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.

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


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera 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.

Powered by Zendesk