Road map of IBM Aspera Proxy
IBM Aspera Proxy server protects your organization’s network while enabling secure, high-speed FASP transfers to and from highly restrictive network environments. Built on top of the Linux kernel, it allows transparent pass-through of FASP transfer sessions across secure DMZs without impeding transfer speeds or compromising the security of your internal network.
its also supports load balancing, high availability, and flexible security policies.
IBM Aspera Proxy Server 1.4.1
Features:
• Sync can now be used with Reverse Proxy with round-robin load balancing.
• FASP transfers through Reverse Proxy can now bind the outgoing TCP/UDP channel to a specific IP address.
• Authenticated HTTP-fallback transfers are now supported by Reverse Proxy.
IBM Aspera Proxy Server 1.4.2
New features:
• Adds reverse proxy support for ascp4 transfers.
• Adds support for dynamic evaluation of individual HTTP Fallback requests by Lua scripting.
• Reverse proxy now supports authentication for HTTP Fallback transfers.
• Transfers through a reverse proxy can now use the bind_source_address option in Aspera. conf which lets users bind an outgoing TCP/UDP channel to a specified IP address.
IBM Aspera Proxy Server 1.4.3
New features:
• The version of NGINX included with Proxy has been upgraded to 1.14.2 to address several security vulnerabilities: CVE-2018-16844, CVE-2018-16845, CVE-2018-16843, and CVE-2019-7401.
IBM Aspera Proxy Server 1.4.4.1
New features:
• Proxy can now be run by a non-root user. For instructions, see the appendix “Running Proxy as a Non-Root User” in the Proxy guide.
• ES-1468 – A new vulnerability in sudo affects the usage of the Runas (ALL) keyword when granting sudo access to users.
IBM Aspera Proxy Server 1.4.5
New features:
• A new configuration option for aspera. conf lets users specify the path to iptables-restore. The option is <iptables_path> and falls under the <server> section. The default value is /sbin/iptables-restore. (ES-1629)
• The forward proxy service and the Redis state store used by the forward proxy server now run under the asperadaemon account. The account is created by the installer if not already on the system.
IBM Aspera Proxy Server 1.4.6
New features:
• Updated Nginx to version 1.20. (ES-2112)
IBM Aspera Proxy Gateway V2.0.1 for Linux
New Features:
• HTTP Gateway
IBM Aspera Proxy Gateway V2.0.2
Features:
• HTTP Gateway now manages ascp processes using the management port defined in gateway config.properties.
IBM Aspera Proxy Gateway V2.0.3
New Features:
• Updated tags in HTTP Gateway ascp transfer tags allow Console to report whether a transfer is an HTTP Gateway transfer or a Connect transfer.
IBM Aspera Proxy Gateway V2.0.4
New Features:
• Updated tags in HTTP Gateway ascp transfer tags allow Console to report whether a transfer is an HTTP Gateway transfer or a Connect transfer.
• Used unique IDs to identify transfers in HTTP Gateway logs.
IBM Aspera HTTP Gateway V2.1.2
New Features:
• You can install HTTP Gateway behind a compatible reverse proxy. IBM Aspera has successfully tested HTTP-Gateway deployments with Nginx 1.16.
• HTTP Gateway now manages ascp processes using the management port defined in gateway config.properties.
• If HTTP Gateway is behind a reverse proxy, HTTP Gateway provides extra information in the ascp transfer tags for use by applications (like IBM Aspera Console) to monitor transfers made with the HTTP Gateway behind the reverse proxy.
• Updated tags in HTTP Gateway ascp transfer tags allow Console to report whether a transfer is an HTTP Gateway transfer or a Connect transfer.
• Used unique IDs to identify transfers in HTTP Gateway logs.
IBM Aspera HTTP Gateway V2.2.0
New Features:
• A web application can now allow downloading a whole folder by providing a folder path instead of the list of files in the folder. (HTTPGTW-148)
• Made improvements to how HTTP Gateway reports the live transfer rate for uploads. (HTTPGTW-117)
• HTTP Gateway transfer specifications now include the file_size property. Applications, such as IBM Aspera Console, that monitor ascp uploads can use this property for progress reports. To show file count progress in Console for HTTP-Gateway-based transfers, customers should be running HTTP-Gateway 2.2.0, HSTS 4.0.1, and Console 3.4.1-PL5 or greater. (HTTPGTW-113)
• New properties in the gatewayconfig. properties configuration file
• Configure HTTP Gateway to write to stdout instead of to syslog using the server config.sys_log_disabled property. (HTTPGTW-168)
• Configure new TLS server settings using the serverconfig.min_tls_version and server config.max_tls_version properties. By default, the minimum TLS version is set to 1.2 and the maximum version is set to 1.3. (HTTPGTW-147)
• Configure HTTP Gateway to allow transfers to only an authorized list of HSTS nodes using the transferconfig.authorized_hsts_nodes property. (HTTPGTW-145)
• Configure ascp transfer sessions to run as a non-root user using the ascpconfig.run_as_user and ascpconfig.run_as_group properties. The configuration only applies when HTTP Gateway is running as root. (HTTPGTW-126)