IBM Aspera Enterprise Server, Connect Server, Point-to-Point, and Client 3.5.5

 
IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.5.5
 

Product Release: June 23, 2015
Release Notes Update: July 7, 2015

WHAT'S NEW

Release 3.5.5 is an update of IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client. It provides the new features, fixes, and other changes listed below. Release 3.5.5 includes IBM Aspera Sync 3.5.5.

New Features

  • The new move-after-transfer feature lets you move source files to a specified archive directory after they are successfully transferred. For the ascp command, the flag --move-after-transfer=archive can be used for either uploads or downloads. The equivalent control from the client GUI is called "Source Move" and has been added to the File Handling tab in the Connection Manager and the New Hot Folder configuration window. From the GUI the feature is available for uploads only.
  • Support for AWS Signature V4
  • Dblogger now passes the <tags> in the fasp session when logging to Console.
  • Improved logging for "Access denied due to invalid authorization."
  • Note: Release 3.5.5 is currently not certified by Aspera for use as a cloud-hosted server. However, 3.5.5 clients can transfer to or from cloud storage.

Other Changes

  • Support for the SSL cipher RC4, also known as ARC4 and ARCFOUR, has been disabled in the Aspera build of OpenSSL.
  • ES 3.5.5 includes the 1.0.1m version of OpenSSL. This OpenSSL update addresses several security issues outlined at http://www.openssl.org/news/secadv_20150108.txt and http://openssl.org/news/secadv_20150319.txt.

ISSUES FIXED IN THIS RELEASE

#29720 - Duplicate folders listed by node

#30068 - Source file not archived when uploaded from UNC path.

#30595 - Source base breaks with some server-side docroot configurations and filelist transfers.

#30612 - Disable support for RC4 in our 3rd-party build of OpenSSL.

#31053 - Bad defaults for the new transfer server SQLite database.

SYSTEM REQUIREMENTS

Windows: 7, 8, 2008r2, 2012
Browsers: Internet Explorer 8+, Firefox 27+, Chrome 32+

Linux 64-bit and 32-bit: RedHat 6-7, CentOS 6-7, Fedora 16-20, Ubuntu 12-14, Debian 6-7, SLES 11-12 Kernel 2.4 or higher and libc version GLIB 2.3.4+.
Browsers: Firefox 27+

Mac OS X: 10.7, 10.8, 10.9, 10.10 
Browsers: Safari 6+, Firefox 27+, Chrome 32+

PACKAGE INFORMATION

Enterprise Server / Connect Server

AsperaEnterpriseServer-ML-3.5.5.107274-windows-32-msvc2012.exe
md5: 8fbd93b718126b33fa56693cd6ddd490
sha1: 147829cdd135d7a8ce3f0209b49a19fd828f8820
aspera-entsrv-3.5.5.107274-linux-32.deb
md5: 0a5f4aab54a70347d06708abb11d7cee
sha1: e8b14281ea6a032a4f0790984e0de94a55091733
aspera-entsrv-3.5.5.107274-linux-32.rpm
md5: 7d75806b11f3308c5ee4d9d2f0d66e39
sha1: ca1c9e12e6bacdf4b2ac3791b38c4f46aab7f4c5
aspera-entsrv-3.5.5.107274-linux-64.deb
md5: b629f83d42becf124fe6c52cf6d24233
sha1: fcb7d7d50241700ae07a17357611377a31f3cbc0
aspera-entsrv-3.5.5.107274-linux-64.rpm
md5: e751b71da1879a6922c47ce9a4f3893d
sha1: 2f2c41ec9a74459b7ca79a6baceeaa2ed090d090
AsperaEnterpriseServer-3.5.5.107274-mac-intel-10.9.dmg
md5: fd10e68d0a4504366d5283aea7e6da10
sha1: 4b9a43ca801da21c7bae721a37c6237f1b8095df

Point-to-Point Client

AsperaP2P-ML-3.5.5.107274-windows-32-msvc2012.exe
md5: 36d89695f7e37e175922f33a374aa00b
sha1: 8fa5fe50e768db636c217627a799d85decc71bc4
aspera-scp-p2p-3.5.5.107274-linux-32.deb
md5: dbe98a1433f847213ac51d36147b3466
sha1: 707698701ba5985c1fb46c606b5b1af9fd640a81
aspera-scp-p2p-3.5.5.107274-linux-32.rpm
md5: 8f9d92259f5fec1956c3b47aafe174b3
sha1: 6a1e48ef633ef0ef09a4eada234cb5f34368908e
aspera-scp-p2p-3.5.5.107274-linux-64.deb
md5: bb6227d15b2e0ee5b7a3735e50af689e
sha1: cbbf23b38ddb6b29edefb273b6bc50bdce114971
aspera-scp-p2p-3.5.5.107274-linux-64.rpm
md5: b74141c64eb76e62aac22efffc49a15a
sha1: eb087a56f0418b497a287689d39a370ceed998fb
AsperaPointToPoint-3.5.5.107274-mac-intel-10.9.dmg
md5: b8299e7ebd8939b5a65e1854fafa80a2
sha1: 796501fba78d7836991cfecdf234b8c19a05cb5c

Desktop Client

AsperaClient-ML-3.5.5.107274-windows-32-msvc2012.exe
md5: a2dcfd247613b075532b240e6887b16e
sha1: bcb8366e00ef0f8d083f39484b473dee0480355d
aspera-scp-client-3.5.5.107274-linux-32.deb
md5: 23c865d26f4ed85b2213720dea294803
sha1: fb6aa2d1f6838fd5cfc0c3b3323cb7c5774e0910
aspera-scp-client-3.5.5.107274-linux-32.rpm
md5: f12f42f7d0ac4b251abfd8385c2f8e80
sha1: 111ea85f6a4ba7e1832ac98df7c3b3a00f662f53
aspera-scp-client-3.5.5.107274-linux-64.deb
md5: 49ba1bd6c91923a343ec278838027f3d
sha1: d038c76f1d5904071693778ac3ec1735114f474d
aspera-scp-client-3.5.5.107274-linux-64.rpm
md5: f9203c2feda53024a4fc9321b4eaae32
sha1: 4cfb2f67e610e52228af0db6f1043a22828c25f6
AsperaClient-3.5.5.107274-mac-intel-10.9.dmg
md5: a5afa78030678527ae0476707e554ab4
sha1: 48ce374e8bc776ec94cccbdc0260c3da30fecad7

KNOWN ISSUES

NOTE: Sync in Drive does not work with ES 3.5.5. For details, see #31418 below. A patch is available for download at the following link:
https://support.asperasoft.com/entries/94847048-ascp-patch-for-ES-3-5-5

#3522 - The aspera.conf.websample from Enterprise Server 2.1.3 is not converted on upgrade.

#4822 - Installing Enterprise Server 2.5 on a machine with a pre-installed cygwin gives an 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 - On OS X, the desktop client's remote file browser hangs on a directory containing over 25,000 files (out of memory).

#5527 - The application may not respond cleanly to the file system it uses becoming full. After making more room, it may be necessary to forcibly shut it down and rebuild the snapshot database before normal operation is restored.

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

#8412 - Backslashes in filenames is not supported.

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

#9126 - Sync logs events at a fast rate. The log destination must have room for large log files.

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

#12972 - A log message is no longer generated for prepost execution.

#13450 - The -C option does not work for special storage (docroot or direct).

#13645 - When a directory is renamed during transfer, Sync continues running and never completes.

#13761 - If filenames contain "\" or new line, async will try to transfer but fail, causing the internal transfer queue to become full and the synchronization to stall (or hang after all the other files have completed).

#13826, #13827, #13833 - Limited support for Unicode filenames on Windows

#16390 - Unicode filenames appear incorrectly in pre/post-processing email notifications.

#16517 - Hot Folders are unable to detect Microsoft Word and PowerPoint file changes.

#16694 - S3 uploads do not resume if the PMTU changes.

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

#18913 - Sync db logging: cancelled or stopped jobs are reported as "completed" in fasp sessions status.

#20347 - Sync reports errors and conflicts for deep directory depth when sync is from Linux to Windows.

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

#20767 - Sync: -R log dir creation from Linux to Windows with spaces in the path will only get as far as the first space in the path.

#20779 - The Connect Server web UI does not respect Groups configuration settings on Windows Server 2012. It restricts the privileges of the user running IIS, and does not allow you to query the group membership of the logged-in user. As a consequence, aspera.conf group settings do not apply.

#20906 - Sync fails to sync a directory after a permission issue has been fixed.

#21014 - When creating a file with 'vi' during a sync, the swap file is in conflict.

#22044 - Sync: asyncadmin reports all sessions locked after the last actual running session.

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

#22633 - Sync does not support large xattr/ResourceForks.

#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, if 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 generate a "no such file" error for any already-transferred files.

#23246 - Warnings are not generated about files skipped due to source base setting.

#23400 - Sync permits root directory to be synced on Linux.

#23434 - Node API: Files that start with "._" are not returned by the Node API browse action.

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

#23876 - On S3, when "always overwrite" is set, files are missing at the destination.

#23954 - Sync: When the --preserve-acls or --preserve-xattrs option is used, async will not preserve the acl or xattr when either file acl or xattr is modified and (a) file content is unmodified or (b) file content is unmodified and the file is renamed.

#24179 - In Connect Server, clicking change user in Internet Explorer brings up a login window where the username field already has the string "user_name" filled in.

#24549 - Drag-and-drop with the 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 - The release notes for Enterprise Server 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 logs each file twice when the transfer is between a source and destination that are on the same node.

#24780 - Sync: both --preserve-acls and --remote-preserve-acls required for a pull.

#24838 - Unable to upgrade to Connect Server from Enterprise Server on Windows. The Connect Server documentation 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.

#25127 - HTTP fallback temporary files (*.haspx) are not filtered out by the Node API.

#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/syncing 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 fails with the error "Data transfer stalled, timed out".

#25832 - Hot Folders: When creating or modifying hot folders, some controls in the File Handling tab do not work correctly:
  • 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.

#25865 - Allowing symbolic links to be copied also allows access to locations outside the docroot.

#25913 - Aspera Drive attempts to sync a file that is still uploading to Shares, resulting in a file error.

#25915 - When the sync function is set to continuous, overwriting an existing file on the initiating node may result in the deletion of the previous version of the file on the responding node. Workaround: Perform the sync manually to recreate the deleted file.

#26185 - During an upload to S3 storage, an error may result if ascp reports a successful file transfer before the transfer to S3 completes.

#26618 - The ascmd process does not exit properly on newer versions of SLES (SUSE Linux Enterprise Server).

#27056 - There is no ascmd support for server-side symlink configuration, which means that 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.)

#27311 - Sync: An apply-local-docroot pull copies local docroot path into docroot path.

#27425 - Cannot install on Ubuntu using the UI. The error message "The package is of bad quality."Workaround: Install from the command line only, as documented.

#27439 - Cannot install on Fedora due to "Missing securiy signature". Workaround: Install from the command line only, as documented.

#27879 - always_set_home does not work if the user's home directory does not exist.

#28288 - When the FIPS mode in aspera.conf is set to true, ascp fails with the error message, "ascp.exe: failed to authenticate, exiting.", without prompting the user for a password.

#28310 - Downloading a folder containing multiple large files from S3 fails to complete when using ascp -C.

#28384 - OSX requires "Legacy Java SE 6 runtime" (Oracle's does not work).

#28747 - Connect Server security: Encryption over HTTP is not enforced, and must be set on the server by an administrator.

#28820 - The following operations attempted in a Limelight directory fail or are unacceptably slow: copy/paste file, rename file, delete folder.

#29038 - The default checksum behavior with S3 (as with any cloud storage) is "none". An existing file on S3 is considered identical to the local file when their sizes are equal. Therefore the file on S3 is not overwritten, even when the content of S3 differs from the content of the local file. Usingoverwrite=always does not overwrite the file.

#29138 - For files in S3, the node daemon does not return the correct file modification time.

#29172 - When using --file-list or --file-pair-list with SoftLayer, some files may not be transferred. Note: This issue is due to a defect in Swift 1.12. Correcting it depends on its correction in Swift and the Swift upgrade on SoftLayer.

#29187 - For content in cloud storage, the Node API does not display all the files in the docroot directory.Workaround: Use the /files/info request to browse the docroot directory when content is in cloud-based storage.

#29255 - Download from SoftLayer of a file larger than 62GB is unsuccessful. Workaround: Do not use time-stamp preservation with SoftLayer.

#29372 - In a Connect Server installation using an Isilon cluster for storage, some icons and checkboxes expected in the directory display are missing.

#30082 - When a Source Move destination is set in the GUI, but the source file cannot be moved, no error message is displayed.

#30131 - The asperacentral server script status is not working in RH7.

#30231 - If a pre-post script includes a path that contains ".." and the client is running on Windows, ascp fails with "cannot open -e pre-post command: Unknown error".

#30277 - In the GUI, when a user right-clicks a hot folder transfer intiiated on another machine and then clicks Edit, nothing happens.

#30572 - Azure produces errors when some types of UTF-8 characters are used.

#30616 - On Isilon, asconfigurator fails with "no space left on device". If this occurs, restart the server so that handles are released.

#31033 - On Azure, creating a file whose name ends with a "." fails. The trailing dot is discarded. On Azure, files cannot end with a "dot" or a "/".

#31418 - Sync in Drive freezes when Drive is used with ES 3.5.5. Activity > Sync shows an empty progress bar. Folders are created but no files are transferred, regardless of whether the sync is push, pull, or bi-directional.

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets, please visit theAspera 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

Article is closed for comments.
Powered by Zendesk