Release Notes: Aspera Enterprise Server, Connect Server, Point-to-Point, and Client 3.5.2
- Product Release: Nov 7, 2014
- Release Notes Updated: Nov 6, 2014
Release 3.5.2 is an update of Aspera Enterprise Server, Connect Server, Point-to-Point, and Client, and provides the new features and fixes listed below. Release 3.5.2 includes Aspera Sync 3.5.2.
- OpenSSL updated to 1.0.1j.
- Ascp HTTP fallback now verifies server certificate.
- Trap - Swift enabled to perform with the Keystone identity service.
- Transfers to S3 now preserve timestamps.
- Ascp parallel uploads to cloud storage.
- Node API now retrieves directory mtime.
ISSUES FIXED IN THIS RELEASE
#17386 - Group docroot inheritance does not work (related to asperanoded).
#24430 - A .partial file remains at the destination after the source file is modified and upload is complete.
#24752 - Node daemon does not send HTTP code 100 (Continue).
#27411 - Folder modification times are not visible in S3.
#27464 - GUI memory leaks can occur with transfers of large set of files.
#27631 - EnableSortByName is broken in 3.4.6.
#27677 - Long pathnames can cause crashes.
#27907 - Windows Connect Server UI tags error
#27940 - Details > Files tab doesn't show files being transferred when you resume a stopped transfer.
#27956 - After a Drive sync, files moved into the local sync directory are reported as conflict files and are not uploaded to the remote.
#28036 - Async bidi -C: When renamed, a Windows server-side directory is not synced.
#28163 -Windows Connect Server: XSS vulnerability
#28244 - Connect Server: click-jacking (Cross Site Request Forgery) vulnerability
#28264 - On OS X, sync fails when the transfer rate is changed through Console.
Windows: 7, 8, 2008r2, 2012
Linux 64-bit: RedHat 6 & 7, CentOS 6 & 7, Fedora 16-20, Ubuntu 12-14, Debian 6 & 7, SLES 11, Kernel 2.4 or higher and libc version GLIB 2.3.4+.
Mac OS X: 10.7, 10.8, 10.9, 10.10
Browsers: Internet Explorer 8+, Firefox 27+, Safari 6+, Google Chrome 32+
PREVIOUS RELEASE NOTES
- Enterprise Server 3.5.1 Release Notes (Windows, Linux, OS X)
- Enterprise Server 3.4.6 Release Notes (Windows, Linux)
- Enterprise Server 3.4.5 Release Notes (OS X)
- Enterprise Server 3.4.4 Release Notes (Windows)
- Enterprise Server 3.3.4 Release Notes (Windows, Linux, [OS X for Client only])
- Enterprise Server 3.3.3 Release Notes (Windows, Linux)
- Enterprise Server 3.3.0 Release Notes (Windows, Linux)
- Enterprise Server 3.1.3 Release Notes (Windows, Linux)
- Enterprise Server 3.1.0 Release Notes (Windows, Linux, OS X)
Linux 64-bit (deb): aspera-entsrv-126.96.36.199065-linux-64.deb
MD5: cf3b3b9f4e966a3ca8f85a4110e93916 SHA1: f43ef927a28c7faec77d2320bfe26d23e8dc69ad
Linux 64-bit (rpm): aspera-entsrv-188.8.131.52065-linux-64.rpm
MD5: a61e51e9fd9abac8584c9cb9f4b53ff3 SHA1: 95282f3a1f65bd90ba493ac28d07b57e8933f20d
Linux 32-bit (deb): aspera-entsrv-184.108.40.206065-linux-32.deb
MD5: fc24944bc7b216601408bf29ab939e35 SHA1: 4199de75182437037ef8df873ba56b97d212149e
Linux 32-bit (rpm): aspera-entsrv-220.127.116.11065-linux-32.rpm
MD5: 8d1b4aca1056fef3856cceb7d5d5d896 SHA1: 95282f3a1f65bd90ba493ac28d07b57e8933f20d
Mac OS X: AsperaEnterpriseServer-18.104.22.168065-mac-intel-10.9.dmg
MD5: af7d537a8f713c67a0913e80706ca837 SHA1: bdda21aba49d41a8174617e8cc0a6b8f787a0d37
MD5: c24509782b76c86f24dc5338a3d30b66 SHA1: 6cf5c23850c6ee18da390419adbb8ad6189f8f2f
Linux 64-bit (deb): aspera-scp-p2p-22.214.171.124065-linux-64.deb
MD5: 80ada3465188cd24649da09cc0ecf416 SHA1: df03e8be1ebdea383a1a7e3a951621bc89dea2a2
Linux 64-bit (rpm): aspera-scp-p2p-126.96.36.199065-linux-64.rpm
MD5: a8328e2d4fa0b595f911628108a825e8 SHA1: d963cf63c0b4cd05a348b5f4d98b88db5279ecae
Linux 32-bit (deb): aspera-scp-p2p-188.8.131.52065-linux-32.deb
MD5: e69dfc21ef9a864ca1e07817271f52e0 SHA1: d056f2112891d4b04e864a99bb8d8643fb72b451
Linux 32-bit (rpm): aspera-scp-p2p-184.108.40.206065-linux-32.rpm
MD5: 3729d3c17775b0a96906da7670e49c39 SHA1: 38369fdf6e51c99196e04556d776f5593104cb9c
Mac OS X: AsperaPointToPoint-220.127.116.11065-mac-intel-10.9.dmg
MD5: 78218c0479d116ebb6252b5eab8ed072 SHA1: b96800f59b73350c3035ac6ac65db48d399e7ed2
MD5: b2a184a9c3ecc109dd1d44f3d24bd980 SHA1: 924701fc0b16e30fd31c5966f494eca46ab63a88
Linux 64-bit (deb): aspera-scp-client-18.104.22.168065-linux-64.deb
MD5: 10f9a1dc0aa0363c15dab0fa0c3849da SHA1: 63a99e008ce8892e0ccf7d7b2f73617aeca14030
Linux 64-bit (rpm): aspera-scp-client-22.214.171.124065-linux-64.rpm
MD5: 375f08046405f3ec2b43e6c37a0c67b5 SHA1: 15e4f12b932f7593170b60a7c7ee350013f7937e
Linux 32-bit (deb): aspera-scp-client-126.96.36.199065-linux-32.deb
MD5: d6e0fdc538fcdfadd5ee9f58fc1a6533 SHA1: bd74e704f1bcee54076d246db3dcd1196438bb5e
Linux 32-bit (rpm): aspera-scp-client-188.8.131.52065-linux-32.rpm
MD5: 538dbb712db249c8f8f50d59c07531c9 SHA1: 455275e03d718b98f414e111bc17bce8caac74d5
Mac OS X: AsperaClient-184.108.40.206065-mac-intel-10.9.dmg
MD5: c3aec2c8558c311bc7b5be5350693c10 SHA1: e3982e5e8b7ff85e6acdc195f8357b2945cede38
MD5: f9e38eed232fb0d68c853e836d96b30d SHA1: 85af77c9dc5d44e4fcd376a1faaeccbb30bc77a9
- Aspera Enterprise Server 3.5.2 Admin Guide (Windows)
- Aspera Connect Server 3.5.2 Admin Guide (Windows)
- Aspera Point-to-Point 3.5.2 Admin Guide (Windows)
- Aspera Client 3.5.2 Admin Guide (Windows)
- Aspera Enterprise Server 3.5.2 Admin Guide (Linux)
- Aspera Connect Server 3.5.2 Admin Guide (Linux)
- Aspera Point-to-Point 3.5.2 Admin Guide (Linux)
- Aspera Client 3.5.2 Admin Guide (Linux)
#3522 - The aspera.conf.websample from ES 2.1.3 does not get converted on upgrade.
#4822 - Installing ES 2.5 on a machine with a pre-installed cygwin gives error message and OpenSSH does not start.
#5079 - Public keys created with 2.2.1 are not installed in the proper directory; as a result, an upgrade to 2.5 may fail to find existing keys.
#5210 - In the desktop client, the File Manifest Path setting does not work with paths containing commas.
#5442 - In OSX, the desktop clients remote file browser hangs on a directory containing over 25,000 files (out of memory).
#5713 - The Windows installer cannot install to a customized folder whose name contains unicode characters.
#6302 - Connect Server on Windows does not support unicode user names.
#6358 - Hot folder transfers fail with unicode user names.
#6443 - If admin A creates a new hot folder and exits the desktop client, and then admin B exits, the new hot folder created by admin A created will be lost.
#6448 - When your regional and language options are set to language standards and formats that do not use "." to represent the decimal point, values are displayed inconsistently using both "." and the native character to represent the decimal point.
#6453 - In the desktop client, changed Preferences settings are not updated under Configuration until the desktop client is restarted.
#6598 - Starting/loading the GUI via SSH-tunneled X redirection takes too long to respond.
#7271 - Sending a file with ":" to Windows causes the creation of an alternate stream. In addition, when partial is enabled, the stream name will remain.partial (the rename to the final name does not work).
#8351 - Failed file paths are truncated to 128 characters.
#8495 - Hot folders do not support the root drive (for example, C:\ or D:\) as the source path. WORKAROUND: Change the source path to point to a subdirectory.
#8534 - IPV6 requires ascp to have the -6 option, which is currently disabled on the server-side if the user is configured for aspshell.
#8538 - If a file fails to be renamed from .partial after it transfers, the transfer is still considered successful and the session will continue (with additional files being renamed successfully). The receiver side logs an error message, but no error is logged on the sender side. WORKAROUND: Successful transfers that were not properly renamed from .partial should be manually renamed.
#8620 - Enterprise Server for Linux fails to install if the dependency perl(CGI) is not installed. WORKAROUND: Install perl(CGI), then rerun the Enterprise Server installation. For example, to install perl-CGI on Fedora, run: yum install perl-CGI. \
#10157 - Connect Server: The Change User button feature (<EnableUserSwitching> in aspera.conf) does not work on Macs if the login credential is saved into KeyChain.
#11550 - If preserve_attributes is set to none on the server side, when downloading a single file with the -p option, the file has an invalid atime value.
#11551 - Group settings under Server Configuration are not being inherited by the group members.
#12854 - The maximum upload size for S3 storage is limited to 625 GB.
#13450 - The -C option does not work for special storage (docroot or direct).
#15897 - From the AWS S3 console, it is possible to rename a folder to have the same name of an existing file. From the desktop client GUI, the folder and file are displayed with the same name. However, if you attempt to download the folder, the file is downloaded instead. Also, uploads to the renamed folder do not complete successfully. Even though it appears in the desktop client that they have completed, the uploaded files are not available at the destination.
#16390 - Unicode filenames appear incorrectly in pre/post-processing email notifications.
#16517 - Hot Folders are unable to detect Microsoft Word and PowerPoint file changes.
#16671 - The Change User button does not work in Safari 6.0.
#16694 - S3 uploads will not resume if the PMTU changes.
#16884 - Resuming a file transfer to S3 starts from the beginning if the destination file already exists.
#17106 - Windows displays dot files, as well as Mac xattr files.
#17218 - On Windows 8, the delivery confirmation receipt is not readable or deletable.
#17243 - An S3 download fails when a filename contains square brackets or a caret.
#17318 - When upgrading, "Run Aspera services as a local SYSTEM account" is enabled by default. In order to preserve the service user from the previous version (for example, svcAspera), you must disable this checkbox. (This applies to admins/users who installed Aspera Enterprise Server on Windows XP and specified a service user -- for example, svcAspera -- rather than a local system account.)
#18659 - Searching with very long pathnames (over 520 characters) results in an "insufficient buffer space" error.
#18832 - Windows Network hot folder stops scanning for new files when clock moves backwards.
#20511 - Connect Server 2.6.3 allowed docroot to be a symbolic link, but 3.1+ does not.
#20576 - Target Rate must be in the range 0 -100 if TargetRateAsPercentage is yes; however, setting a target rate greater than 100 does not return an error. (Note that rate percentage is a deprecated feature.)
#20617 - The SOAP API does not return an error when invalid values are passed into any of a number of parameters. Instead of returning an error, a transfer is either created with a default value, or the bad value is passed to ascp where it will fail.
#20779 - The Connect Server Web UI does not respect Groups configuration settings on Windows Server 2012. It restricts privileges of the user running IIS and we are not able to query group membership of the logged-in user. As a consequence, aspera.conf group settings do not apply.
#22552 - The Node API browse call returns file system details using a non-existent transfer user on WinXP.
#22618 - The behavior of the Node API "paths" filter changed with ES 3.4. It now returns only the directory matching the filter, not the directory's content.
#22619 - In the Node API, file searches now follow symbolic links.
#22848 - On S3, uploading a file to a non-existent destination path, and without the -d option, creates the destination path anyway.
#22905 - On S3, when copying a file with ascp, and a slash is appended to the destination -- for example, /path/ -- the file is renamed path/. Because of the trailing slash, it appears to be a directory, but is actually a file.
#22998 - If the overwrite setting in the server's aspera.conf is "deny", a destination file with the same name as the transfer file is still overwritten.
#23070 - If a transfer of several files is interrupted, the retries will generate a "no such file" error for any already-transferred files.
#23246 - Warning are not generated about files skipped due to source base setting.
#23337 - An invalid payload for Node API *load_setup does not return an error.
#23434 - Node API: Files that start with "._" are not returned by the Node API browse.
#23503 - Akamai: Uploads of zero-byte files appear to be successful, but no file is present at the destination.
#23583 - Certain option values for asperacentral job submission are case sensitive.
#23791 - When faspcat forwarding is enabled, faspcat does not read aspera.conf for file permissions mode.
#23876 - On S3, when "always overwrite" is set, files are missing at the destination.
#24179 - In Connect Server, clicking change user in IE brings up a login window where the username field already has the string "user_name" filled in.
#24549 - Drag-and-drop with Linux version of the desktop client is not supported. Attempting a drag-and-drop upload does nothing. Attempting a drag-and-drop download causes the mouse cursor to display a plus sign, suggesting incorrectly that the feature is available.
#24638 - Release notes for ES 3.3.0 say that with the new Node API, "Support for async session set up on behalf of client". No API for this is available.
#24671 - DB logger is logging each file twice when the transfer is between a source and destination that are on the same node.
#24690, #23516 - On certain versions of Fedora Linux, the desktop client can fail to start or exits suddenly with an "assertion failed" DBUS error. This is rare but can occur.
#24838 - Unable to upgrade to Connect Server from Enterprise Server on Windows. The Connect Server doc says you can do this from Control Panel > Add or Remove Programs as long as IIS has been configured. However, An error message tells you to create a website in the IIS manager, even if the website already exists. WORKAROUND: Uninstall Enterprise Server, then install Connect Server.
#25042 - In the server-side aspera.conf, the none option for file checksum reporting is no longer supported; only md5, sha1, and any are supported. The any option means allow the checksum format to be whichever format the client requests. On the client side, the none option is still available, as a command-line option. A setting of any on the client side results in an error with the message "ascp: unknown file checksum type any".
#25083 - When hot folder transfers fail due to lack of permissions, the hot folders tab gives no indication that the failures are due to insufficient permissions.
#25631 - When transferring from Windows to Mac using preserve-acls=native and remote-preserve-acls=native, ACL data is saved as xattr. Workaround: Do not use the "native" setting when transferring/sync'ing across platforms.
#25636 - To use a larger chunk size to transfer big files to AWS S3 storage, some users modify the memory settings in the trapd initialization script, asperatrapd_init.sh. If you do so, be sure to preserve the script manually during upgrades to prevent it from being overwritten.
#25791 - Azure: concurrent upload failed with the error "Data transfer stalled, timed out".
- The option for resuming incomplete files does not work, but is still necessary to enable options for checking whether files at the source and files at the destination are the same.
- Selecting Compare File Attributes only checks whether the files are the same size.
- Selecting Compare Sparse File Checksums actually compares full checksums.
#25897 - Files counter increases when a file is still being moved to the source folder.
#25979 - The following error message may appear on Windows: "JET RUNTIME HAS DETECTED UNRECOVERABLE ERROR". The problem is caused by a mismatched DLL, which may result when an Aspera product upgrade is incomplete. To correct the problem, uninstall the Aspera product, manually delete the "bin" and "lib" directories from the Program Files Aspera installation directory, and reinstall. Another possible cause is bad system DLLs that may have been replaced by your antivirus system. To correct, uninstall the antivirus package and make sure the problem no longer occurs.
#26379 - Google Scp: hot folder table display incorrect format and data.
#26386 - Google: When there are concurrent uploads, some are stopped due to "Data transfer stalled, timed out".
#26427 - Akamai: Some concurrent transfers are stopped with the error "Insufficient Permissions".
#26446 - Pvcl-trap - Need to limit the number of buffers used for uploads.
#26481 - Node API - cannot modify transfer with a put request.
#26480 - Node API - transfer stuck in idle status when no one is listening to mandatory management port.
#27056 - No ascmd support for server-side symlink configuration, which means the application GUI functionality is still the same as in 3.4.6. (For additional information, see the WHAT'S NEW description of new server-side configuration options for symbolic links.)
#27218 - If Shares is set to use EAR, downloads of unencrypted content via HTTP fallback will fail with numerous errors. Common errors include: "Insufficient permissions", "Server refused request", and "Connection Lost".
#27879 - always_set_home does not work if the user's home directory doesn't exist.
#27924 - Installing on CentOS 7 on Google Cloud requires that perl and the perl module Data::Dumper be installed first.
#28384 - OS X requires "Legacy Java SE 6 runtime" (Oracle's do not work).
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.