Release Notes: Aspera Connect Browser Plug-In 3.7.4

Product Release: September 18, 2017
Release Notes Updated: September 19, 2017

Welcome to the 3.7.4 release of the IBM Aspera Connect Browser Plug-in for Windows, Linux, and Mac OS X. This release provides improvements to accessibility.

NEW FEATURES

  • Connect 3.7.4 provides improvements to accessibility.
  • [MacOS] Improved security. Connect has been built with Apple recommended security settings.
  • Support for AES-256 encryption, as long as both client and server are running ascp 3.7.3 or higher.
  • Transfers are now encrypted by default.

SYSTEM REQUIREMENTS

Note: If you use Connect with the IBM Aspera Add-in for Microsoft Outlook, you must upgrade to the latest release of the Outlook Add-in before installing and using this release of Connect.
Windows
  • OS versions: 7, 8, 10, or Windows Server 2008 R2, 2012 R2, 2016
  • Browsers: Microsoft Edge, Internet Explorer 8-11, Firefox 27-55, Chrome 32-61
Linux (64-bit)
  • OS versions (glibc 2.9 and higher): RHEL 6-7, CentOS 6-7, Fedora 16-20, SLES 11-12 and openSUSE 42.2, Ubuntu 12-15, Debian 6-7
  • Browsers: Firefox 27-55, Chrome 32-61
  • Required Libraries: OpenSSL 1.0.2g or higher, Mesa EGL, glib2 2.28 or higher
MacOS X
  • OS versions: Mac OS X 10.8 - 10.12
  • Browsers: Firefox 27-55, Chrome 32-61, Safari 6-9

PREVIOUS RELEASE NOTES

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-connect-3.7.4.147727-linux-64.tar.gz
md5: 37e667b90217fa6c00a61c0329637afa
sha1: 14b52dadc1cb5d61dfc768c92a0ba972f3d2fd82
Mac OS X: AsperaConnectInstaller-3.7.4.147728.dmg
md5: cb910b5ab89459f7d5683e42b4e9c17f
sha1: 6b3942f263fb214312dececc4f28cb96d532eae5
Windows: AsperaConnect-ML-3.7.4.147728.msi
md5: c304c46f694e050732ac64a280486ffa
sha1: 48f0adcc87fa2e10e5052b05af6a66456fb09dad

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-355, ATT-470 - 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.

ASCN-347 - When the Shares setting for Allowed Policy is set to "fair and low", Connect sets the transfer policy to "fixed".

ASCN-346 - [Linux] The Connect icon is not being used in the taskbar and start menu.

ASCN-324 - Transfers fail when <allowed_cipher> is set to aes-192 in the server's aspera.conffile. Workaround: Set <allowed_cipher> to aes-128 or aes-256.

ASCN-264 - The Connect setup wizard for uninstall shows "Installing Aspera Connect..."

ASCN-245 - Content uploaded via fallback using Connect 3.7 (plugin) and EAR cannot be downloaded using the 3.6 plugin.

ASCN-234 - Connect accumulates hundreds of transfer status events while the "Upload folder" dialog box is up.

ASCN-198 - Connect gives the error message "Path contains unsupported characters" when a folder is downloaded to Windows with an illegal path (regression).

ASCN-190 - [Windows] Cannot run first instance of user and administrator asperaconnect.exe at the same time

ASCN-179 - This release of Connect does not support Microsoft ISA proxies.

ASCN-148 - Connect does not display all the digits in the Transfer Monitor when there is increased system text size. (CIM-280)

ASCN-131 - Entering badly formatted hostnames (http://hostname vs. hostname) causes all transfers to fail with "FASP process failed to initialize" (Code: 1003).

ASCN-119 - When the default debugging level is set to Info, Connect adds DBG (debug) entries to its logs.

#33004 - [Windows 10] When filenames contain Nepali script, they do not display correctly in Connect's Transfers window. Other Unicode characters do display correctly.

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

#32446 - [Windows] If you perform a system-wide installation of Connect, Aspera recommends that you not use the built-in Administrator account for this installation. The built-in Administrator account includes privilege settings that are too high, resulting in various issues in Connect capabilities. Most importantly, your users will not be able to drag and drop files in the Connect interface, in any browser. Instead of the built-in Administrator account, Aspera recommends that you use a different administrator account for system-wide installation.

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