Release Notes: IBM Aspera Connect 3.10.0

Product Release: August 18, 2020
Release Notes Updated: August 17, 2020

The 3.10.0 release of IBM Aspera Connect provides the new features, fixes, and other changes listed below. These release notes also list system requirements, supported platforms, and known issues.

NEW FEATURES

  • Improved performance with large numbers of files
  • Multi-session transfers. This feature increases transfer speed for very fast network connections (>1Gbps). (ASCN-1104)
  • A new application preference to bypass FASP proxy, similar to the HTTP proxy bypass found in web browsers. The bypass option lets you specify a list of host addresses, IP addresses, or IP subnets. (ASCN-2311)
  • Security confirmation has been simplified, and the confirmation dialog has been redesigned. (ASCN-2116)
  • Users can now do offline distribution of Edge extension. (ASCN-2074)
  • A new function has been added for calculating file checksums. (ASCN-1832)
  • Connect now supports the overwrite_policy key in the transfer spec for transfers started programmatically. (ASCN-540)

Aspera plans to deploy the Connect 3.10 SDK as the default SDK on Cloudfront in 60 days.

  • [SDK] New option to replace the IBM Aspera banner for custom installation experiences. (ASCN-2304)
  • [SDK] ipv6 is now recognized and a new option lets developers specify that the transfer should use ipv6. (ASCN-2138)
  • [SDK] A new option allows specifying a list of remote hosts for multi-session transfers. (ASCN-2000)
  • [SDK] The transfer name in the Connect UI can now be changed from the API. (ASCN-1854)
  • [SDK] New function to test for SSH connectivity. (ASCN-1606)
  • [SDK] Connect activity API now shows the number-of-files summary. (ASCN-1439)
  • [SDK] The Connect SDK implementation has been improved with the support of promise syntax. (ASCN-1059)
  • [SDK] Added trusted-host confirmation to other sensitive APIs, thereby expanding the scope of Connect SDK functionality covered by security confirmation. (ASCN-818)

FIXED ISSUES

  • ASCN-2298 - In the Activity View, some transfers cannot be retried or deleted.
  • ASCN-2279 - [macOS] Starting Connect in the sandbox by the package-maker installer generates the error "FASP process failed to initialize".
  • ASCN-2250 - [macOS] Connect does not work with Chrome Canary because the app is not detected.
  • ASCN-2140 - [SDK] Some timestamps in the transfer info are unstable, such as add_time and modify_time.
  • ASCN-2054 - Upgrading Connect sometimes fails to keep the older version of Connect closed.
  • ASCN-1803 - [Win] Downloads fail (Code:56 error) if file or folder names end with a trailing space.
  • ASCN-1758 - [Win] UI: When multiple transfers are queued, dialogs may appear out of order.
  • ASCN-1601 - [SDK] [Win] The showDirectory API does not bring the Explorer dialog to the foreground.
  • ASCN-1432 - [Mac] Connect crashes when multiple modal windows are displayed at the same time.
  • ASCN-1318 - [Mac] Connect on Mac 10.14 does not detect system proxy settings. Workaround: Configure the proxy manually in Connect preferences.
  • ASCN-898 - The error message "Connect (Not Responding)" appears after clearing hundreds of transfers.
  • ASCN-355, ATT-364 - When using HTTP fallback, downloads with in-line decryption sometimes fail after an upload to a server with EAR. Workaround: Download without in-line decryption, then decrypt locally.

SYSTEM REQUIREMENTS

Note on browsers: The version numbers shown are for those browsers on which Connect was verified at the time of release; however, Connect is likely to work on later versions.

OS Versions Browsers
Windows
  • Windows 8.1, 10
  • Windows Server 2016, 2019
  • Chrome 80-84
  • Firefox 72-79
  • Firefox ESR 68, 78
  • Internet Explorer 11
  • Microsoft Edge (Chromium) 84
  • Microsoft Edge (Legacy) 43-44 *
Linux
  • RHEL 7, 8
  • CentOS 7, 8
  • Debian 9, 10
  • SLES 11, 12
  • Fedora 31, 32
  • OpenSUSE 15
  • Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS
  • Chrome 80-84
  • Firefox 72-79
  • Firefox ESR 68, 78
macOS
  • macOS 10.13 - 10.15
  • Chrome 80-84
  • Firefox 72-79
  • Firefox ESR 68, 78
  • Safari 12-13
  • Microsoft Edge (Chromium) 84
  • * Aspera plans to discontinue support for Microsoft Edge (Legacy) in a future release.

KNOWN ISSUES

  • ASCN-2301 - Chrome does not detect Aspera Connect when the username contains an ampersand (&).
  • ASCN-2274 - After upgrade, IE11 does not detect Connect until the browser is restarted.
  • ASCN-2272 - [macOS] System proxy settings are not effective until the Connect app is restarted.
  • ASCN-2232 - [Linux Gnome] Excessive system notifications appear saying "IBM Aspera Connect is ready".
  • ASCN-2203 - [macOS] Connect 3.10 has no dark-mode support.
  • ASCN-2069 - With file splitting, multi-session uploads are not distributed equally and incorrect transfer stats are reported.
  • ASCN-2036 - Connect does not start automatically after a system-wide installation or upgrade. Workaround: launch Connect manually to fix the issue automatically.
  • ASCN-1971 - Linux browsers installed using Snap cannot launch Connect.
  • ASCN-1958 - A previously running transfer will be relaunched on application startup only if it is retryable
  • ASCN-1852 - [Windows] Drag and drop fails when Chrome runs in high mandatory integrity mode. Workaround: Don't run as the built-in Administrator. (CIM-2690)
  • ASCN-1851 - [Windows] Connect fails to open file dialogs when the browser's security integrity level is higher than Connect's. Workaround: Don't run as the built-in Administrator.
  • ASCN-1829 - [Mac] Upgrade: progress bar stuck 'Verifying "Aspera Connect"...' Workaround: The stuck progress bar is related to Apple virus scanning and can usually be resolved by restarting the Connect application.
  • ASCN-1698 - Connect crashes when user attempts to trust host too quickly.
  • ASCN-1557 - After upgrading, drag-and-drop does not work until the browser is restarted.
  • ASCN-1487 - [Mac] Safari extension-approval step appears even if the installation started in a different browser.
  • ASCN-1295 - When encrypted files are downloaded, there is no "Protected Content" dialog asking for a passphrase to unlock the files being transferred or to keep the files encrypted. The files are still downloaded, so the files can be decrypted later after download.†
  • ASCN-797 - Main menu bar for Crypt is not translated for all languages.
  • ASCN-754 - [Windows] Internet Explorer crashes during a Connect upgrade.
  • ASCN-705 - If Connect is not able to connect to the server through SSH, a misleading error message, "Failed to authenticate," is reported rather than indicating it's a connection problem. (CIM-72)
  • ASCN-580 - [Windows] Accessibility: Install wizard not properly displayed in high contrast mode.
  • ASCN-271 - When encrypted-at-rest files are downloaded, the decryption dialog does not ask for passphrase confirmation. As a result, if the passphrase is invalid, the files are transferred in their encrypted state. (CIM-635)
  • ASCN-262 - JAWS does not say how to select hosts from the hosts list in the Security sub-tabs. This issue is found in other Security sub-tabs, as well.
  • ASCN-149 - Connect does not switch "desktops" to reveal Connect when asking the user to select files or folders. Workaround: Select Connect from the dock.

PRODUCT SUPPORT

For online support, go to the IBM Aspera Support site at https://www.ibm.com/mysupport/. To open a support case, log in with your IBMid or set up a new IBMid account.