Product Released: May 17, 2024
Release Notes Updated: May 17, 2024
This patch release of IBM Aspera Connect 4.2.10 covers a support fix, system requirements, and
known problems. A list of fixed issues and new features from previous releases is also included.
Releases:
- 4.2.10
- 4.2.9
- 4.2.8
- 4.2.7
- 4.2.6
- 4.2.5
- 4.2.4
- 4.2.3
- 4.2.2
- 4.2.1
- 4.2.0
- 4.1.3
- 4.1.2
- 4.1.1
- 4.1.0
New
features
4.2.3
| Summary |
Ticket |
| New transfers are now placed at the top of the list in the Activity window and older
transfers are removed after the max limit (100) is reached. |
Aspera/connect-app#412 |
| Apple Silicon native builds of Connect are now available in Fix Central. |
Aspera/connect-app#1473 |
4.2.0
| Summary |
Ticket |
| Connect 4.2.0 now supports Faspex 5.0. |
Aspera/connect-app#1409 |
| Alphabetically sort workspaces in the Inbox settings section. |
Aspera/connect-app#1375 |
| [Windows] Registering the Aspera Drive shell extension can now be disabled during the
Connect installation. |
Aspera/connect-app#1139 |
| [macOS] The Connect package installer (.pkg) now supports both system-wide and per-user
installations. |
Aspera/connect-app#901 |
4.1.1
| Summary |
Ticket |
| [Windows] The Aspera Drive folder only appears in the Explorer navigation pane when you add
accounts in Connect. |
Aspera/connect-app#685 |
4.1.0
| Summary |
Ticket |
| When connecting to Faspex 5 BETA, Connect uses your default browser for OAuth 2
authorization to Faspex 5 BETA resources. |
Aspera/connect-app#713 |
| Connect supports the Faspex 5 BETA. Send and download packages and browse nodes using
Connect. |
Aspera/connect-app#168 |
Breaking
changes
4.2.0
| Summary |
Ticket |
| Connect 4.2.0 no longer includes the DSA private key. On the ascp
command line, you will not see -i/path/to/asperaweb_id_dsa.openssh. |
Aspera/connect-app#1392 |
Documentation
updates
4.1.0
| Summary |
Ticket |
| Upgraded the importance of a note that warns customers not to enable debug or trace logging
unless needed due to impact on performance. |
Aspera/connect-app.docs#20 |
Issues fixed in this
release
4.2.9
| Summary |
Ticket |
| [macOS] Connect crashes when trying to browse remote file systems. |
Aspera/connect-app#1991 |
4.2.8
| Summary |
Ticket |
| When Connect auto downloads a package from Faspex 5, the Faspex 5 UI package summary shows
0 downloads. |
Aspera/connect-app#1905 |
4.2.7
| Summary |
Ticket |
When calling the function /read-chunk-as-array-buffer, and the offset is
bigger than 4 GB it results in an overflow that causes the chunk to be incorrect. |
Aspera/connect-app#1950 |
| [macOS] Connect application window opens up and takes away focus from the application when
the transfer is initiated via Connect. If you minimize the Connect Window, it opens up again
repeating the same behavior. |
Aspera/connect-app#1919 |
| [macOS] Connect does not respond or crashes when multiple (100+) transfers remain in the
activity window. |
Aspera/connect-app#1911 |
4.2.6
| Summary |
Ticket |
Stale token warning is being displayed repeatedly under
Preferences > Accounts tab
. |
Aspera/connect-app#1896 |
[macOS] Files not being filtered correctly in the Select File dialog when
allowedFileTypesis set. |
Aspera/connect-app#1892 |
| When users enabled "Always ask me where to save downloaded files", Connect creates an empty
directory. |
Aspera/connect-app#1890 |
Package downloads display the SSH username instead of the Faspex account username due to a
missing cookie field from the transfer spec. |
Aspera/connect-app#1868 |
| Connect pull sync: remote file deletion does not trigger local file deletion. Asynchronous
database resets after every poll. |
Aspera/connect-app#1804 |
4.2.5
| Summary |
Ticket |
| [Windows] Issues while adding a Faspex 5 account to Connect have been resolved. |
Aspera/connect-app#1799 |
| IBM Aspera Connect 4.2.5 fixes a buffer overflow issue. |
Aspera/connect-app#1795 |
| The Faspex 5 automatic package downloads feature now uses the SSH port specified by the
server. |
Aspera/connect-app#1768 |
4.2.4
| Summary |
Ticket |
| [macOS] The preferences window now properly saves when changing multiple
settings. |
Aspera/connect-app#1760 |
| The "Allow access to computer" prompt window is now displaying properly and no longer
missing the "Yes" and "No" buttons. |
Aspera/connect-app#1147 |
4.2.3
| Summary |
Ticket |
| Downloading an already existing file no longer causes Connect to become unresponsive when
specific download settings are selected. |
Aspera/connect-app#1651 |
| Gatekeeper sometimes blocks the installation of Connect/Cargo on macOS. |
Aspera/connect-app#1637 |
Connect no longer crashes when AW4.Connect#getChecksum is called from the
SDK. |
Aspera/connect-app#1573 |
4.2.2
| Summary |
Ticket |
| ascp crashes when --file-checksum is enabled. |
Aspera/connect-app#1555 |
4.2.1
| Summary |
Ticket |
| Connect only checks up to 50 workspaces for package downloads. |
Aspera/connect-app#1478 |
| Connect v4.2.0 crashes on macOS 10.13 - 10.15. |
Aspera/connect-app#1521 |
4.1.3
| Summary |
Ticket |
| Connect app is missing app group entitlement. |
Aspera/connect-app#1298 |
4.1.2
| Summary |
Ticket |
| Content Security Policy blocks inline scripts and inline event handlers. |
Aspera/connect-sdk#92 |
| Browsing Aspera on Cloud workspaces only displays the first 25 workspaces. |
Aspera/connect-app#723 |
| [mas OS] The Connect icon is not properly displayed in the macOS menu bar. |
Aspera/connect-app#1178 |
FASP URL transfers are using the dgram_sz option, resulting in
intermittent packet size errors. |
Aspera/connect-app#1244 |
4.1.1
| Summary |
Ticket |
| When setting up automatic package downloads with Aspera on Cloud, users only see the first
50 workspaces instead of all available workspaces. |
Aspera/connect-app#1155 |
|
Connect does not provide a completion event after successful transfer when configured to "remove
transfer list items upon successful transfer".
|
Aspera/connect-app#1079 |
| On smaller monitors, the Connect Preferences window is too large, preventing users from
saving preferences. |
Aspera/connect-app#1070 |
|
You cannot permanently dismiss the "Node not syncable" message after exhausting retries.
|
Aspera/connect-app#1049 |
| Users cannot add a Shares account using Okta 2FA. |
Aspera/connect-app#1032 |
|
Users cannot add a Faspex account to Connect using Okta 2FA.
|
Aspera/connect-app#1027 |
Connect does not use the --check-sshfp
ascp parameter. |
Aspera/connect-app#960 |
| Reduced the scope of permissions on Connect web extensions to address a security
concern. |
Aspera/connect-app#896 |
| There is an assortment of translation and localization errors. |
Aspera/connect-app#881 |
| [macOS] The Preferences option is missing from the Apple Menu. |
Aspera/connect-app#756 |
| [Windows] Connect is slow to start when Connect is configured to run many concurrent
instances of Connect. |
Aspera/connect-sdk#71
|
4.1.0
| Summary |
Ticket |
| [Windows] Download silently continues even after user presses stop button during
"Connecting" phase. |
Aspera/connect-app#771 |
| [Linux] Unable to launch IBM Aspera Connect on some Linux machines with the error "Could
not load the Qt platform plugin 'xcb'". |
Aspera/connect-app#669 |
| [macOS] Visual glitch appears on Accounts page when starting transfers with a new
server. |
Aspera/connect-app#660 |
| Drive (now Connect) intermittently crashes during AoC sync. |
Aspera/connect-app#605 |
|
Removed the word "dummy" in codebase to align with inclusivity guidelines.
|
Aspera/connect-sdk#69 |
Other
changes
4.2.10
| Summary |
Ticket |
| Updated support for macOS 12.7 and later. |
Aspera/connect-app#2238 |
4.2.9
| Summary |
Ticket |
| Connect now uses OpenSSL V3. |
Aspera/connect-app#1557 |
4.2.4
| Summary |
Ticket |
| Chrome extension updated to manifest V3. |
Aspera/connect-app#1641 |
4.2.3
| Summary |
Ticket |
| UI keyboard shortcuts for Aspera Crypt and opening the About window have been
updated. |
Aspera/connect-app#1634 |
4.2.0
| Summary |
Ticket |
| We no longer provide one-click installer for Connect in Windows or macOS. |
Aspera/connect-app#1264 |
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 11
- Windows 10
- Windows Server 2019
|
- Chrome 108
- Firefox 108
- Firefox ESR 102.6.0
- Microsoft Edge 108.0
|
| Linux |
- RHEL 8
- CentOS 8
- Debian 11
- SLES 15
- Fedora 35, 36, 37
- OpenSUSE 15
- Ubuntu 20.04 LTS
|
- Chrome 108
- Firefox 108
- Firefox ESR 102.6.0
|
| macOS |
- macOS 12.7 and later
- If customers are using macOS 11.0 or earlier, please upgrade to the latest supported macOS
version or use Connect 3.11.
|
- Chrome 108
- Firefox 108
- Firefox ESR 102.6.0
- Safari 16.1
|
Server Requirements
One of the following:
- IBM Aspera Shares - a currently supported version
- IBM Aspera Faspex - a currently supported version
- IBM Aspera High-Speed Transfer Server (HSTS) - 3.9.6 or higher recommended
To use Connect's Aspera Drive synchronization features, the server must have a Sync-enabled
license.
The minimum version of Connect that works with the Connect SDK is
3.9.0.
Known
issues
4.2.0
| Summary |
Ticket |
| [Windows] In some cases, you might not be able to access the Aspera Drive shell extension
after upgrading to Connect 4.2.0. Workaround: Manually restart Explorer or reboot the
machine. |
Aspera/connect-app#1325 |
4.1.3
No known issues discovered in 4.1.3
4.1.2
No known issues discovered in 4.1.2
4.1.1
No known issues discovered in 4.1.1.
4.1.0
| Summary |
Ticket |
[macOS] The current one-click installer does not support a system-wide install on macOS.
Workaround: To do a system-wide install on macOS with the current one-click installer:
- Log in as an Administrator of the machine.
- Open the binary distribution file (.dmg file) to mount the installer
- Run:
sudo /Volumes/ibm-aspera-connect_4.1xx_macOS_x86_64/IBM\ Aspera\ Connect\ Installer.app/Contents/Resources/install true
|
Aspera/connect-app#901 |
| Windows Explorer crashes in some situations trying to view package files in Faspex 5 BETA.
Note: This issue will be resolved in future updates to Faspex 5 BETA.
|
Aspera/connect-app#811 |
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.