Enterprise Server 3.0.0 Release Notes
For Enterprise Server, Point-to-Point, Client, and Connect Server
Created: September 7, 2012
Modified: September 24, 2012
Created: September 7, 2012
Modified: September 24, 2012
- Features the new Aspera Node API, a daemon that offers REST-inspired file operations and a transfer management API. The Node API has the following functionality:
- Provides an HTTPS (by default port 9092) and HTTP (by default port 9091) interface.
- API encoded in JSON.
- API is authenticated and the node daemon uses its own application-level users (i.e., "node users").
- Features a node admin utility called “asnodeadmin,” which can be utilized to add and manage "node users."
- Logs to syslog, akin to asperacentral.
- Support for Amazon S3 storage (i.e. connections to “the cloud”)
- New time stamp preservation options (ascp and SCP)
- New rate control option (aspera.conf)
- (Linux) Aspera fasp Proxy, Aspera's open and authenticated proxy solution built on top of the Linux kernel. Aspera Proxy Server addresses the following use case:
- Your enterprise security environment limits general Internet access, including the fasp protocol. Employees cannot access Aspera servers from their desktops and your IT department would like to implement an authentication requirement for Aspera clients initiating connections to the outside. Or, if you use the Connect browser plug-in within your network, you do not have visibility or control over fasp transfers into and out of the network.
- Updated the behavior for adding and removing connections within the Enterprise Server GUI. When managing connections, changes will not be saved until you click the OK button. Clicking Cancel will discard any unsaved changes made in the Connection Manager, including the addition and removal of connections.
- Numerous bug fixes and UI improvements.
- Updated UI for new configuration options.
- AS11/DPP media file format validation
- IMPORTANT: If you have upgraded from 2.7.X to 3.X on Windows, please be aware that user names are now case sensitive.
- (#4822) It is not recommended to perform a “Typical” installation of Enterprise Server on a machine with another copy of Cygwin installed (this requires additional manual steps for the installation to work and manual steps to restart the SSHD service). The recommendation is to uninstall Cygwin (if it's not needed) or perform a “Custom” install. During the “Custom” install, you can deselect the SSHD server option that is included in the package by default and use a third-party SSHD server (such as Bitvise).
- (#5210) The “File Manifest” setting in SCP does not work with paths containing commas.
- (#5442) On Mac, the maximum number of files in a single directory that SCP can browse without failing is 200,000.
- (#5713) The Windows Enterprise Server installer cannot install to a custom directory that contains unicode characters in its name.
- (#6302) Connect Server on Windows does not allow unicode user names.
- (#6358) Hot Folder transfers fail with unicode user names.
- (#6598) Starting/loading the GUI via SSH-tunneled X redirection takes too long to respond.
- (#6443) If (1) Administrator A creates a new Hot Folder and exits SCP, then (2)Administrator B closes SCP, the new Hot Folder that Administrator A created will be lost.
- (#6448) When your regional and language options are set to language standards and formats that doesn't use "." to represent the decimal point, values are displayed inconsistently using both "." and the native character to represent the decimal point.
- (#6453) If you modify a setting in the SCP “Preferences” screen that affects the settings in the “Configuration” screen, you must restart SCP before you see the new settings under “Configuration.”
- (#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 doesn't work).
- (#8351) Failed file paths are truncated to 128 characters.
- (#8495) Hot Folders do not support the root drive (i.e. C:\ or D:\) as the source path. Workaround: Change the source path to point to a subdirectory.
- (#8522) If .partial cannot be moved to the final name, this event is still reported as a success.
- (#8534) IPV6 requires ascp to have the “-6” option, which is currently disabled on the server-side if the user is configured to 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 re-run the Enterprise Server installation. Here is an example command to install perl-CGI on Fedora: “yum install perl-CGI”.
- (#10391) On Solaris x86 servers running Connect Server, new folders with unicode characters created through the “New Folder” button do not appear correctly. This behavior has been noticed on servers running Apache 2.2 and Perl 5.8.4 with 32 or 34 patches. Workaround: Refresh the web page.
- (#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.
- (#12335) The Aspera Enterprise Server GUI may freeze or appear incorrectly in Windows 7 when switching to/from a high-contrast display theme.Workaround: To prevent ES from freezing/appearing corrupted, you must restart the application after changing Windows’ theme settings.
- (#12358) Applies to the ascp command “--user=USERNAME” when used with a Windows server. On Windows, If you do not specify a user name for the transfer, the local username will be authenticated (by default). In the case of a Windows machine and a domain user, the transfer server will strip the domain from the username (e.g. authenticating "Administrator," rather than "DOMAIN\Administrator). Thus, you will need to explicitly specify a domain, if applicable to the user, to perform a successful transfer. Note that this also requires Aspera services (including OpenSSH) to be running under a domain user.
- (#13084) Related to Node Proxy. If the node restarts (or the computer restarts), all NAT rules will be cleared. As a result, all active fasp sessions will timeout and retry based on their application retry rules.
- (#13138) There is a known vulnerability with Windows IIS servers running ASP.NET applications. This vulnerability affects Aspera Connect Server in a minimal way (i.e., temporary DoS attack); however, it’s not an issue that Aspera can fix. Aspera customers who are concerned about the Windows vulnerability can run Aspera Connect Server on any other supported Operating System (e.g. Linux, Mac, Solaris, FreeBSD), or Aspera Shares (for Linux) as an alternative product.
- (#13450) The -C option doesn't work for special storage (docroot or direct).
- (#15971) Persistent sessions for S3-direct connections (i.e., transfers to S3 through a relay user) are not supported for this release.
- (#16390) Unicode filenames appear incorrectly in Pre/Post processing email notifications.
- (#16456) Uploads via an Azure-direct connection (no doc root specified inaspera.conf) to Azure fail when transfers are attempted to root (/). Although using the root of the account is legal, this requires a specific syntax and is discouraged by Microsoft.
- (#16517) Hot Folders are unable to detect Microsoft Word and PowerPoint file changes.
- (#16671) The Change User button (experimental feature) on Connect Server doesn't 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.
- (#17243) When a filename contains square brackets or a caret, an S3-download fails.
- (#17318) This applies to admins/users who installed Aspera Enterprise Server on Windows XP and specified a service user, e.g. svcAspera (rather than a local system account). When upgrading to Enterprise Server 3.0, the “Run Aspera services as a local SYSTEM account” is enabled by default. In order to preserve the service user from the previous version (svcAspera), you must disable this checkbox.
- (#17386) Related to asperanoded - group docroot inheritance is not working properly. Workaround: Set global docroots or individual user docroots.
- 50e867e7ba291fa08415e3699a9be473 aspera-entsrv-184.108.40.206716-linux-32.deb
- db31055beccbb56118fbcc07f524d9d5 aspera-entsrv-220.127.116.11716-linux-32.rpm
- 310faa91cc9f833179871cdb88b91623 aspera-entsrv-18.104.22.168716-linux-64.deb
- 290630af56ccf46f9e64b3a588f91c43 aspera-entsrv-22.214.171.124716-linux-64.rpm
- cc8fa30e89a2c23c6c9053da59b00ae1 aspera-scp-client-126.96.36.199716-linux-32.deb
- dd091f53d578a48fc4a31c5e7a1c1515 aspera-scp-client-188.8.131.52716-linux-32.rpm
- 7e5c5b7e689c109006e19c8930be11cd aspera-scp-client-184.108.40.206716-linux-64.deb
- f960b8a89cd652e4fbc46f4bbb0c4f90 aspera-scp-client-220.127.116.11716-linux-64.rpm
- 1bc80b5e2ca9d05d88d9c8f305b35d0c aspera-scp-p2p-18.104.22.168716-linux-32.deb
- 5e41d27446f30901a67776e8ab4b10bc aspera-scp-p2p-22.214.171.124716-linux-32.rpm
- 819bd26e814f07a4cb11faf1743e862e aspera-scp-p2p-126.96.36.199716-linux-64.deb
- c70c2acc7895980cdc8e2fcbaa44d196 aspera-scp-p2p-188.8.131.52716-linux-64.rpm
- 616fc870ca3940952cc7f562173626c6 AsperaClient-184.108.40.206733-windows-32.exe
- 4689d2e241ed8e57c4871ba14ad7a81d AsperaP2P-220.127.116.11733-windows-32.exe
- b4062020e149a67daca469bcebc16a2e AsperaEnterpriseServer-18.104.22.168733-windows-32.exe
- b257b26da3096b9773b1f196213745bf6d74f072 aspera-entsrv-22.214.171.124716-linux-32.deb
- 2454772b0f4afa89417623ad62201af88d16a171 aspera-entsrv-126.96.36.199716-linux-32.rpm
- d6e63f6108c969c2875da6de99f4ddfbac0c2b1a aspera-entsrv-188.8.131.52716-linux-64.deb
- fdff8fc4915a73b568faad025fcc071896aa9d39 aspera-entsrv-184.108.40.206716-linux-64.rpm
- 1e79720ea6d60be9ed65c39161885e3a282e0251 aspera-scp-client-220.127.116.11716-linux-32.deb
- 7dcdfba4852d8eb9aa710c59a929de925f833f50 aspera-scp-client-18.104.22.168716-linux-32.rpm
- 72ef53538799780f5ea15d12e67f1c2961ba5f77 aspera-scp-client-22.214.171.124716-linux-64.deb
- 7d1dc3b689bef2a069c825d2336fdb5843bb1502 aspera-scp-client-126.96.36.199716-linux-64.rpm
- 8545897e66d56a01f4da678fb227325f98890944 aspera-scp-p2p-188.8.131.52716-linux-32.deb
- c83bdd83d9f168eaa5ccb94dd3b126a75b78f440 aspera-scp-p2p-184.108.40.206716-linux-32.rpm
- 0383d03d15cfe707f1d7b04f66563a510dce2b52 aspera-scp-p2p-220.127.116.11716-linux-64.deb
- e5d65dca09f86bc9bf395c11f7bb7fb452661e6f aspera-scp-p2p-18.104.22.168716-linux-64.rpm
- afbbffa6a63fa66603e4e7d11681d5882980dc65 AsperaClient-22.214.171.124733-windows-32.exe
- 21e9938fe899ae371cb802bb88f4d161f2e8192f AsperaP2P-126.96.36.199733-windows-32.exe
- 5b3604da294c7642c27536e2f75cbad37717bd06 AsperaEnterpriseServer-188.8.131.52733-windows-32.exe