Release Notes: Aspera Connect Browser Plug-in 3.7.1 (Linux)

Product Release: March 1, 2017

Release Notes Updated: March 1, 2017

Welcome to this release of the IBM Aspera Connect Browser Plug-in for Linux platforms.

NEW FEATURES

  • The Connect troubleshooting tool (https://test-connect.asperasoft.com) has been incorporated into the banner that appears when Connect appears not to be installed. (CIM-48)
  • Connect no longer limits the number of concurrent transfers to 100. The Transfers window displays the first 100 active transfers, along with a count of the remaining transfers. In these cases, for each transfer you delete from the Transfers window, another remaining transfer then appears.
  • The Connect SDK features several API enhancements. For detailed information, see the Aspera Developer Network at https://developer.asperasoft.com .
  • If you host the Connect SDK on your own servers, it is now loaded from there.

BREAKING CHANGES

If you are upgrading from a previous release, the following changes in this release may require you to adjust your workflow, configuration, or usage:
  • ASCN-189 - [32-bit Linux only] Connect is no longer supported for 32-bit Linux distributions.
  • ASCN-170 - Depending on your Linux distribution and version, you may need to update your OpenSSL installation in order to allow Connect to launch. The required minimum version of OpenSSL is 1.0.2g. To install and build it, perform the following steps:
    1. Log in as root.
    2. Download the source for OpenSSL 1.0.2g or higher.
    3. Build OpenSSL:
      # ./config shared -fPIC -dPIC
      # make depend
      # make
      # make install
    4. Add OpenSSL to your path:
      # ln -s /usr/local/ssl/bin/openssl /usr/bin
    5. Replace libssl.so.1.0.0 and libcrypto.so.1.0.0 in /lib/x86_64-linux-gnu:*
      1. Copy /usr/local/ssl/lib/libssl.so.1.0.0 to /lib/x86_64-linux-gnu.
      2. Copy /usr/local/ssl/lib/libcrypto.1.0.0 to /lib/x86_64-linux-gnu.

      *The location and filenames for libssl and libcrypto may vary for different distributions. To verify what's used in your environment, you can search for the string libssl in the Connect logfiles.

ISSUES FIXED IN THIS RELEASE

Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.

ASCN-159 - The default string for the resume_suffix value in aspera.conf files is now .aspera-ckpt (Aspera checkpoint).

ASCN-128 - A number of issues with Japanese translations have been fixed.

ASCN-113 - When transfer content is encrypted, Connect now prompts you for the passphrase only once. (CIM-192)

ASCN-100 - If a transfer contains multiple files, the transfer status of each file transferred is available through the Connect API.

ASCN-48 - [Firefox only] Mozilla has announced that Firefox will drop plugin (NPAPI) support in the first quarter of 2017. In anticipation of this change, Connect can now operate without the NPAPI plugin. The Connect installer does install the NPAPI plugin for cases when the plugin is needed for servers running older versions of the Connect SDK.

ASCN-36 - If you are not using token authentication, the password was visible in the Connect logfile. (CIM-58)

ASCN-21 - If your transfer server is configured for content protection_allowed=true, Connect did not support transfers when the wrong password is entered.

#34355 - [Chrome and Firefox] 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.

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

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

#30299 - A bug was fixed in which Chrome warned of "mixed content," and the HTTPS lock showed a warning.

SYSTEM REQUIREMENTS

Linux
  • OS (64-bit):
    • RHEL 6, 7
    • CentOS 6, 7
    • Fedora 16-25
    • SLES 11; openSUSE 42.2
    • Ubuntu 12-16
    • Debian 6-7
  • Browser: Firefox 27-50 or Chrome 32-55

PACKAGE INFORMATION

KNOWN ISSUES

Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.
  • ASCN-179 - This release of Connect does not support Microsoft ISA proxies.
  • ASCN-177 - [Chrome only] Due to a bug in Chrome, the wrong name is displayed in a pop-up dialog. The dialog displays the following:
    Open xdg-open?
            Always open links for xdg-open
    The dialog should display Connect instead of xdg-open.
  • ASCN-172 - [Fedora only] On Fedora 25, 64-bit, the Connect GUI does not display correctly in the Adwaita desktop environment theme. Workaround: Change the default theme to one of the following, for example:
    • Clearlooks
    • Crux
    • Industrial
    • Mist
    • Raleigh
    • ThinIce
  • ASCN-119 - When the default debugging level is set to Info, Connect adds DBG entries to its logs.
  • ASCN-32 - [Chrome only] The JAWS screen reader cannot read the message in the Faspex web application that asks permission to launch Connect in order to start uploads. The issue stems from an aspect of the Chrome browser.
  • #32908 - Connect can display an unnecessary proxy configuration dialog.
  • #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