Release Notes: Aspera Connect Browser Plug-in 3.6.2

Product Release: February 12, 2016
Release Notes Updated: February 12, 2016

WHAT'S NEW

Welcome to this release of the IBM Aspera Connect Browser Plug-in. This 3.6.2 release completes the migration of Connect from NPAPI to the new framework for the Chrome browser, and features maintenance changes and improvements.
Note: The 3.6.2 release is for Linux platforms only.

ISSUES FIXED IN THIS RELEASE

#34355 - [Chrome only] Connect formerly used ports in the 33003 range for local host communication, but now uses 43003 ports. If you use an antivirus program for local host traffic, you should configure it to allow ports 43003-43012. Other browsers are unaffected, and continue to use ports in the 33003 range.

#33861 - [Firefox only] Because of a change in Firefox's requirements, Connect no longer includes a web installer for this browser. Instead, to use Connect with Firefox, you can download the installer and then install Connect.

#32980 - [Linux only] Users could not install or run Connect if another user on that computer was also running Connect.

#32744 - [Linux only] Aspera Web applications did not detect Connect when it was already installed.

#32726- For transfer servers that host the Connect SDK locally, the default behavior has changed as to which location is used. Connect now uses the location specified in the web application (Faspex, Shares, Console, or a custom app) to load the API files, installer code, and plugins (if an upgrade is needed). If these files are not found on the web application server, the production server (CloudFront) is used. This change was made to improve the robustness of local serving of the Connect SDK package.

#32646 - [Linux only] Connect on Linux had a dependency on the lsof utility. This dependency has been removed.

#32261 - [Windows and Linux only] Firefox 40.x had intermittent issues with a number of browser plug-ins, including Connect, in which plug-ins crashed unexpectedly.

#30299 - Chrome issued a warning icon and log messages about "mixed HTTP and HTTPS content."

SYSTEM REQUIREMENTS

Linux
  • OS:
    • RHEL 6, 7
    • CentOS 6, 7
    • Fedora 16-20
    • SLES 11
    • Ubuntu 12-14
    • Debian 6-7
  • browser: Firefox 27-43 or Chrome 32-47

PACKAGE INFORMATION

Linux 32-bit (rpm): aspera-connect-3.6.2.117442-linux-32.tar.gz
md5: 9a95a503827a76cce82b31e8a5b0469b
sha1: 6b7671046e675a9fcbaf715e46fe57a3cf406d2e
Linux 64-bit (rpm): aspera-connect-3.6.2.117442-linux-64.tar.gz
md5: 8abc62cbe04ad424055191fa59c7057a
sha1: 53ca7888ca49eca6c85928b4adf1ef14c9cce080

KNOWN ISSUES

  • #32868 - [Linux only] When you use Connect with Chrome 46 and higher and an authenticated proxy, Chrome does not recognize Connect.
  • #32716 - In Chrome 45 and higher, the browser may not detect that a previous version of Connect is installed. You can follow the steps to download and install Connect.
  • #32402 - [Linux only] There are issues with the automatic detection of available updates for Connect. However, the Aspera web applications (Aspera Faspex, Aspera Shares, and Aspera Console) will alert you if an update to Connect is required.
  • #32379 - [Linux only] On Linux platforms, you cannot use Connect to drag and drop files.

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.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk