Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.6.3 for Mac OS X

Product Release: September 20, 2016

Release Notes Updated: September 11, 2017

This release of IBM Aspera Enterprise Server, Connect Server, Point-to-Point, and Client for OS X provides the new features, fixes, and other changes listed below. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. Additional sections list system requirements and known issues.



  • Support for the following Aspera products, including later releases: Aspera Files 1.0.0, Shares 1.9.3, Console 3.0.3, Connect 3.6.2, and Aspera On-Demand 3.6.0 (for AWS, Azure, and SoftLayer), and ATCM 1.0.0 (Aspera Transfer Cluster Manager).
  • Aspera introduces access key authentication for Ascp and Sync. Access keys provide an alternative to the security credentials of a node user or system user. Because an access key is restricted to its own storage (local or cloud), it allows access control and usage reporting to be segregated by storage. This offers significant benefits to multi-tenant service providers and enterprise installations with multiple departments. Access key authentication supports Aspera client products, such as Desktop Client, Point-to-Point Client, Enterprise Server, Connect, and Drive. It also supports Faspex, Shares, and Aspera Files. For details, see your product documentation for these products.
  • The ascp command now supports multiple private SSH key files that are called on the command line, specified with -i arguments. The keys are tried in order and the process ends when a key passes authentication or when all keys have been tried and have failed authentication.
  • Added support for tokens for parent paths in single path transfers. For example, a token built for /general also allows a transfer of a single file or directory named /general/other/subsidiary.
  • Added support for the hmac-sha2-256 and hmac-sha2-512 algorithms.
  • Added support for the diffie-hellman-group-exchange-sha256 key-exchange algorithm.
  • The default read/write block size is now 256 K (262144 KB) in ascp.
  • The option ascp --remove-empty-source-directory for the --remove-after-transfer feature can now be enabled in Aspera Central in the SOAP API; it removes the source directory itself.
  • The command to resume ascp with the command-line argument k2 or k3 now works when an FIPS-140 compatible cipher is set.
  • A new option in aspera.conf for client-side encryption setting frees users from having to specify a matching value at the command line (-T).
  • The ascp for forward proxy supports DNS names pointing to multiple proxies.
  • Added a client-side configuration option to define a per-user or global default of the SSH key (to help clients used to running ssh without specifying a key if $HOME/.ssh/id_rsa exists).
  • Support for full URIs in file lists and file-pair lists.
  • Support for the multi-session threshold feature in node (file.json) transfers.
  • The response to an ops transfer get request now includes job_state in the list of transfer sessions.
  • Java SNI support is now available for HTTPS requests.
  • A new ascp option, --remove-empty-source-directory, removes the root source directory after a transfer. This option is a companion to --remove-empty-directories, which deletes subdirectories but not the root source directory.
  • Users can now run asnodeadmin --db-update to migrate data from Enterprise Server 3.5.6 and earlier versions.
  • Server-side encryption-at-rest (EAR): EAR encryption and decryption can now be done from the server. The passphrase is set in aspera.conf. Client-side EAR is still available as before.
  • A new option, session_timeout_sec, can now be set in aspera.conf.
  • A new asnodeadmin option, --show-transfer-queue, allows the node admin to view the current queue of transfers.
  • A new asnodeadmin option --show-transfer-log allows the node admin to view all transfers (ongoing, completed, failed, orphaned, and so on), except for those currently in the transfer job queue.
  • A new option, Delete empty source subdirectories, has been added to Connections > File Handling. This option is used in conjunction with the options for moving or deleting source files after transfer, neither of which moved or deleted source subdirectories. Note that this option does not remove the root source directory.
  • Users are now able to set a policy for retrying node-to-node transfers. These options are set in aspera.conf and the node API.
  • Ascp has a new option, --delete-before-transfer, for deleting extraneous files at the transfer destination. Files that are "extraneous" are those that exist at the destination, but not at the source. A new utility, asdelete, provides the same capability from the command line.
  • On the DBLogger, options for the persistent store (ignore_empty_files, ignore_no_transfer_files, ignore_skipped_files, and file_errors) are now configurable in aspera.conf.
  • License support is now available for multiple entitlements per computer.
  • Source files can now be deleted after transfer using the --remove-after-transfer option with ascp or async, or from the desktop UI (Connections > File Handling > Automatically delete source files after transfer). This feature does not remove directories.
  • It is now possible to bind asperanoded to a specific address.
  • Users can now include customizable fields in the subject line of transfer notification templates.
  • The save-before-overwrite feature no longer requires the sending or receiving client to use --partial-file-suffix.
  • The ascp command has new options for preserving OS X extended attributes (xattrs) and Windows Access Control Lists (ACLs), regardless of the type of file system storage: --preserve-xattrs, --remote-preserve-xattrs, --preserve-acls, --remote-preserve-acls.
  • Docroots can now be configured using $(home) for a user's home directory. This is also supported by asconfigurator.

Node API

  • In Node API, the parameters iteration_token and after_time can now both be used with the APIs /ops/transfers and /events; the parameters can be used together or separately. The parameters are set in aspera.conf according to the following policy:
    • If no value is available for count, use the value set in max_response_entries.
    • If count is present, return the lower number of responses of count and max_response_entries.
  • Node API transfer jobs can be split into multiple ascp sessions to take advantage of multiple computers or multiple cores and I/O streams on a single computer. This is governed by two parameters: (1) the ascp option -C, which enables multi-session transfers (also known as parallel transfers) and specifies how many sessions to run per job, and (2) a new ascp option --multi-session-threshold=threshold which specifies whether to split large files equally between sessions, or have each session transfer full files. For cloud storage, file-splitting is currently supported for S3 only. For details, see Ascp Command Reference in the Admin Guide for Enterprise Server, Connect Server, Point-to-Point Client, or Desktop Client.
  • Node API /transfers and /opt/transfers take a multi_session field to split a given transfer job between multiple ascp sessions, possibly over multiple nodes when using a cluster as an initiator. Functionality: this adds a default multipart aspera.conf configuration directive to use when one is not specified by the API call.
  • Users can now specify token lifetime using *_setup in the Node API. Previously this was only possible using an astokengen option.
  • It is now possible to preserve the UID, GID, and timestamps to the Aspera Central SOAP API with a job order.

Watchfolder and Aspera Watch Service

  • A new Aspera WatchD service (asperawatchd) provides ultra-fast file-system change detection and a snapshot service for speed, scale, and distributed sources. The watch service discovers changes in source file systems (new files, new directories, deleted items, renamed items, and so on) immediately as they occur, eliminating the need for scanning the file system. It can be used on any local host or shares host (CIFS, NFS). The watch service integrates with the following:
    • Aspera Sync for fast synchronization of large numbers of files without scanning.
    • Ascp for fast detection and sending new and deleted items.
    • The new Aspera Watchfolder feature for a fast, scalable watchfolder.
  • A new watchfolder feature automates file transfers from a source to a destination system. Files placed into a designated source folder are automatically transferred to the destination. Watchfolder transfers are run from the source machine only and do not require any additional software on the destination system.
  • Added support for encryption-at-rest (EAR) in the watchfolder configuration.
  • aswatchadmin now allows specification of the escape character when using --format.
  • asperawatchd now supports domains (namespaces) in redis that distinguish the different asperawatchd instances running on the same redis instance, which enables asperawatchd to start multiple asperawatchd instances using different users.
  • A new procedure removes the --master option from asperawatchd and introduces a procedure to elect a leader among the running daemons. This helps to overcome the situation where the master instance crashes or loses the connection to the other instances.
  • asperawatchfolderd support for aspera proxy (dnat/dnats).

Cloud Support

  • Improved performance (by increasing the speed) when the system is deleting a large number of files in Azure.
  • Transfers to Amazon S3 storage now have the capacity to set cache-control request headers. For more information, see the API Reference in the AWS documentation at the following URL (subject to change):
  • Support for Amazon KMS when uploading to S3 (pushes data directly to S3 and supports KMS encryption).
  • Amazon's new Infrequent Access storage option is now available as a storage class, through docroot configuration.
  • Folders created in s3Fox (Firefox plugin directory) are displayed with the conventional directory name structure (filename/) in the Enterprise Server UI when is edited to set the following property to true: = true.

    If the default property ( = false) is not edited, the directory name displays as filename_$folder$ when the user restarts Trapd and browses to the folder in the UI.

  • File links are now supported for cloud storage. The "links" are small text files have the following naming convention:
    Limitations: The current implementation (of uploads) does not check whether a file with a -lnk name already exists at the destination, and pvcl_trap does not handle the symlink type, hence the "symbolic link" symbol is not displayed in the UI.
  • Clients that are 3.4.6 or later can now use SSH to upload or download to/from a 3.5.6 server on an Azure cluster. Note, however, that top-level buckets can be reached only through SSH.
  • Added support for storage to blob pages in Azure.

Aspera Sync

  • Aspera Sync now preserves POSIX attributes in the event that file attributes change but file contents do not (times, UID, GID).
  • Aspera Sync now supports periodic scans on remote.
  • Aspera Sync now accepts external cookies, tags, and reports.
  • Aspera Sync: When using the --keep-dir-local or --keep-dir-remote options, locating the keep-dir under the same directory as the sync directory is no longer an error condition as long as the keep-dir has been added to the exclude list.
  • Aspera Sync: A new option, --scan-interval, allows the user to run a periodic scan in async. This new option takes a time spec.

Other Changes

  • This release offers a new set of aswatchadmin options reorganized by function, which can be used instead of the --tool option. The first command below is replaced by the second:
    aswatchadmin --db-spec redis:localhost:31415 --tool=daemon --create /mnt
    aswatchadmin create-watch /mnt --db-spec redis:localhost:31415


  • When you export and import connections in the GUI, they do not include passwords. Because the password database encryption uses a per-user/per-machine cryptographic key, the encrypted passwords cannot be used on other machines. Since the passwords are not transferred, they must be re-entered when the connection is imported. This is an intentional change in behavior that was made for security reasons.
  • Mac OS X 10.7 and earlier versions are no longer supported. Workaround: Upgrade the operating system to Mac OS X 10.8 or newer.
  • When using multi-session (parallel) transfers, there is a version incompatibilty between 3.5 clients and 3.6 and newer servers. This is due to the change in how files are split and how the splitting of individual files is configured on both versions. Workaround: Upgrade the client side to 3.6 or newer.
  • For Mac OS X 10.11 (El Capitan) users, the System Integrity Protection feature of the operating system blocks SSH-based services. A workaround is documented in Aspera Enterprise Server Admin Guide: Product Setup.
  • The aspera.conf options for asperawatchd snapshot creation have changed.


#33742 - Node API /files/browse uses a configurable aspera.conf option to retrieve the preserved modification times for ascp uploads.

#33122, #33104 - If a node has <preserve_times> set in aspera.conf, Faspex 3.6.2 and older will break. However, Faspex will not break if <preserve_attributes> is any, which is the default.

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

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

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

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

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

#24671 - DB logger logs each file twice when the transfer is between a source and destination that are on the same node.

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

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

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

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

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

#5442 - On OS X, the desktop client's remote file browser hangs on a directory containing over 25,000 files (out of memory).

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


Mac OS X: 10.8, 10.9, 10.10, 10.11 (El Capitan)
Browsers: Safari 6-9, Firefox 27-48, Chrome 32-50


Enterprise Server 3.5.5 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.4 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.2 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.5.1 Release Notes (Windows, Linux, OS X)
Enterprise Server 3.4.5 Release Notes (OS X)
Enterprise Server 3.3.4 Release Notes (Windows, Linux, [OS X for Client only])


Enterprise/Connect Server

Mac OS X: AsperaEnterpriseServer-
md5: f916d9a065db1ae83ed5e7c8f04617b1
sha1: 2ee194886167882d1e2b5e145dc5dc28dd557945


Mac OS X: AsperaPointToPoint-
md5: 486ed9c7f4d2da5b4b1c75ecff147b20
sha1: a76283a8d5b337ee84e23ff4f537ce8706b9dc2c


Mac OS X: AsperaClient-
md5: 5408b987a11e099d066a2e9025528622
sha1: 3394749ca74e310806552b5c80e6197e15cd25c0


Note: This release contains tickets created from different tracking systems. For this reason, the ticket IDs may reflect different numbering formats.

#ES-49 - In Mac OS X, the product manual doesn't open when the user clicks Help > Manual in the GUI if the Preview application is not already running. Workaround: The manual can be opened from the Finder, or by launching Preview before clicking Help > Manual.

#WAT-174 - Watchfolder uses excessive memory when watching 10 million files.

#WAT-169 - [Watchfolder] When using top_level_dirs drop detection with x top level directories, 7(x)+ drops are created. The drop count continually increases.

#36373 - In cases of a failed transfer, the files counter in session statistics is not updated with the data for skipped files.

#36276 - When the <ignore_skipped_files> setting is enabled (true) on the ES node, Console continues to show all skipped files for failed transfers on the Activity page.

#35952 - asunprotect cannot decrypt a re-protected file.

#35453 - Parallel transfers from the desktop client to Enterprise Server (ES 3.6.0 and above) with the -C option fail with the error Session Stop (Error: Session initiation failed).

#35255 - When Japanese characters that include the voiced sound mark are used to name a directory in Connect Server, the following issues may occur:
  • The upload fails without an error message.
  • The download fails with the error code 43: The specified path cannot be found.

#34811 - The user is unable to download encrypted files with an incorrect decryption passphrase when using HTTP fallback.

#34674 - When Japanese language is set on the ES UI, it doesn't respect aspera.conf settings; all docroot settings are set to false, and the other settings fail with attached Japanese errors.

#33877 - Aspera Enterprise licenses that are watchfolder-enabled don't display watchfolders as an enabled setting when running the license switch ascp -A.

#33374 - The unimplemented function error does not appear when the user attempts to create a symbolic link to a file on cloud storage (S3) from the Node API. (Symbolic link capability is only available on local storage.)

#33229 - The client is no longer able to browse a file on cloud storage using a /files/browse API request.

#33214 - Transfers to and from cloud storage (S3)—using authorization tokens with URIs that do not have a docroot specified—are unsupported.

#33206 - /ops/transfers erroneously shows some queued transfers (which are farther down in the queue) as failed before they have completed.

#33202 - Node API allows the user to move a file in cloud storage into a directory with a /files/rename request.

#33094 - ascp delete-before-transfer does not support URI storage.

#32941 - Because pvcl does not support the --no-read --no-write option, ascp should fail transfers that use these options with pvcl. However, ascp ignores the options and continues the transfer.

#32890 - In a successful transfer from the client to the server, ascp fails to copy the metafile and thus it does not transfer with the data file.

#32669 - When a directory is linked from a subdirectory, it does not appear in the search result for a /files/search request in the Node API.

#32627 - When a filename is just a dot and an extension, (for example, .pdf), then it is reported as a file with "content_type"=>"application/pdf" or a hidden file named PDF; for example:
{"id"=>"27", "name"=>".pdf", "size"=>12, "content_type"=>"application/pdf", "type"=>"file", "modified_time"=>"2015-09-10T15:24:01Z", "access_level"=>"edit", "permission_count"=>0}

#32553 - When the FASP Session log source file list exceeds 500 bytes and contains multibyte UTF-8 characters, the output is truncated in a manner that creates an invalid UTF-8 sequence.

#32517 - Retransfer requests are unencrypted when transfers are encrypted. This can cause transfer failures in some scenarios, such as a network device dropping the retransfer request because it detects a bit sequence it considers malicious.

#32080 - An error message spams the log file used by asperanoded each time the console attempts to check the node for the status. A second error can occur when the end user fills in a docroot but doesn't have a valid system user; this results in an error that also spams the log file used by asperanoded.

#31712 - For both AWS and Softlayer Swift storage, /files returns modified_time for files but not for folders.

#31423 - It is possible for an ascp transfer of a file on a full disk to be reported as successful by both the sender and the receiver.

#30690 - ascp fails with an inaccurate message—Error: failed to authenticate—when a server is configured to only accept ciphers that are no longer supported.

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

#30542 -/files PUT (file rename) should be fixed to involve only one PVCL operation but still return the proper 409 code when there is a destination conflict, and PVCL needs to return proper error codes stating that the move operation failed because of a destination conflict.

#29848 - When <write_allowed>, <read_allowed>, and <dir_allowed> are all set to false in aspera.conf, Node API calls to URLs such as /files/browse are returning response code 500 Internal Server Error: instead of another code that better indicates that access to the resource is denied.

#29787 - When the docroot is not configured, the HTTP error code 500 ("Internal Server Error") is returned.

#29255 - Download from SoftLayer of a file larger than 62GB is unsuccessful. Workaround: Do not use time-stamp preservation with 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.

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

#29078 - When an access key is created using the standard node user authorization, the access key inherits that node user and its associated system user. Afterwards, asnodeadmin can be used to associate a new system user to the node user, but the new system user is not updated for the access key.

#28939 - If command line ascp neglects to specify a destination host, then the failed transfer (error: "no remote host specified") gets recorded in SQLite with client_node_id NULL, instead of being populated with the uuid of the node. This causes an issue with Console.

#28887 - When a file or directory is moved using the --exclude command, the old file or directory is not removed from the remote side.

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

#28686 - Multi-session uploads to S3 with file splitting must have the ascp chunk size and the S3 part size set to equal values. (File-splitting only works with S3.) File-splitting needs to respect a minimum split size, which for cloud storage is a part. That is, each ascp call needs to deliver full parts. Minimum split size is specified with the ascp option --multi-session-threshold. However, note that if the file size is greater than the multi-session threshold and smaller than the chunk size, then there is no split. Set chunk size and part size as follows:
  1. In aspera.conf set the chunk size to some value greater than 5 MB; for example:
    <chunk_size>67108864</chunk_size>   <!-- 64 MB -->
  2. In /opt/aspera/etc/trapd/
    • Set the upload part size (default 64 MB) to the same value as the chunk size.
    • Use a ONE_TO_ONE gathering policy:

#28683 - docroot warning message: If global docroot is enabled, reports the root user as insecure.

#28679 - In some cases, the fallback server does not respond.

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

#28219 - asperanoded fails to delete a directory name containing backslashes. Workaround:
  1. Stop node.
  2. At the command prompt, issue the command ulimit -S -n 2048.
  3. Restart node in the same command-line shell (the limit is shell-specific).
  4. Send in the same /files/delete request as you did before; the head and everything in it will be removed.
Note: Prior to the command in Step 2 above, you can find out the current limit by running the following command: ulimit -a | grep "open files".

#27908 - When asperacentral has database errors, it continues to allow new transfers.

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

#27823 - The user's Faspex Server goes down with an "Transfer Server errors detected" error message. An error, "trying to read events from a parser that already reported an error before" appears. Workaround: Move the central-store.db to allow re-creation.

#27056 - There is no ascmd support for server-side symlink configuration.

#27007 - Aspera clients on UNIX systems use the HTTP_PROXY and HTTPS_PROXY environment variables when configured to use a FASP proxy; it does not report this in the logs. These variables are not used in HTTP Fallback.

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

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

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

#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, If you do so, be sure to preserve the script manually during upgrades to prevent it from being overwritten.

#25467 - async can now be used with a cloud storage.

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

#25042 - In the server-side aspera.conf, the none option for file checksum reporting is no longer supported; only md5 and sha1 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".

#24805 - For a synced directory, while all of the files and subdirectories under the source folder will have ACL preserved at destination, the ACL for the source folder itself will not be replicated to the remote destination folder.

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

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

#23583 - Certain option values for asperacentral job submission are case-sensitive.

#23503 - Akamai: Uploads of zero-byte files appear to be successful, but no file is present at the destination.

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

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

#23070 - If a transfer of several files is interrupted, the retries generate a no such file error for any already-transferred files.

#23004 - Console does not draw a line between the involved nodes for an async transfer. This issue occurs when using two managed nodes with two interfaces on two different networks.

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

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

#22848 - On S3, uploading a file to a non-existent destination path, and without the -d option, creates the destination path anyway.

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

#22619 - In the Node API, file searches now follow symbolic links.

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

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

#21629 - Connect Server does not accurately reflect file permissions for user actions.

#20906 - async can't create a watch on an unreadable directory; therefore it does not get notified when permissions change. In addition, async treats an unreadable directory as "skip" rather than reporting an error or conflict.

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

#20002 - Inconsistent behavior regarding symbolic link following: /files/browse doesn't follow the links and reports links and their target (final type and next name), while /files/info reports symbolic links as files or directories.

#19945 - asyncadmin creates SHM and WAL files for read-only operations. Once asyncadmin is run as the root, async run by the user does not have permission to access the existing SHM and WAL files and thus async fails. This is due to a bug in SQLite.

#18913 - Sync database logging: cancelled or stopped jobs are reported as completed in fasp_sessions.status.

#18780 - An async push conflict occurs when a new file is renamed quickly.

#18659 - Searching with very long pathnames (over 520 characters) results in an "insufficient buffer space" error.

#18530 - FASP and Sync now accept and verify SSH remote-host keys.

#18368 - Files with a backslash in the filename are not displayed in the list when the user browses the remote source on the new package page.

#17243 - An S3 download fails when a filename contains square brackets or a caret.

#16911 - Characters in the async session option that are not preceded by a "-" or "--" are ignored, therefore failing to trigger an error message. Any session options specified (such as -l or -a) after the string of characters not preceded by a "-" or "--" are also ignored. The session will still run, using the default values, without notifying the user that the new settings have not been applied.

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

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


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.

Powered by Zendesk