Aspera Shares 1.8.1 Release Notes

Product Release Date: Sept 5, 2014

Release Notes Updated: Sept 8, 2014

WHAT'S NEW

This release of Aspera Shares 1.8.1 for Linux (x64) provides the following new features:

Manager: Administrators can now assign "manager" permissions to users, groups, or directory services for a given share. Users with the “manager” permission gain administrative privileges to their assigned share and can create/manage new or existing users and groups within the managed share.

Encryption-at-Rest: Implemented the ability to decrypt files while downloading. Downloading encrypted files when Shares is set to use Encryption-at-Rest (EAR) will now prompt for a password to decrypt them.

Stats-collector: Performance improvements.

KNOWN ISSUES

#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, you need to set the desired values in the aspera.conf file on the node.

#15396 - The transfer fails when attempting to download special files like symlinks, block and character device files, socket, etc.

#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 will not encounter this problem.

#27187 - If the node is set to use Encryption-at-Rest (EAR) but the 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 doesn't prompt the user for a password.

#27188 - If Shares is set to use EAR, downloading a file that wasn't encrypted shouldn't ask for a passphrase.

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

#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to login. Workaround: Turning off "Extended Protection" in ADFS SAML IdP will at first produce random ADFS SAML user login failures with "Invalid SAML response" error and infinite redirects on login, but will fix the problem long run.

SYSTEM REQUIREMENTS

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

OTHER RESOURCES

PRODUCT SUPPORT

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.