GoAnywhere Gateway Release Notes

April 22, 2020 - Version 2.8.1

  • Fixed an issue where the key store type was not defaulting to JKS when not supplied for configurations using Control SSL or SSL Termination.

April 20, 2020 - Version 2.8.0

  • Added support for SSL Termination and SSL ReWrapping.
  • Fixed an issue where an extra line feed or carriage return would cause a license to be invalid.
  • Upgraded Apache Commons-Collections from 3.2 to 3.2.2.
  • Upgraded the Netty library from 4.1.44 to 4.1.48.

January 31, 2020 - Version 2.7.0

  • Added online license capabilities, which include activating a license programmatically using the online activator from the GoAnywhere Customer Portal.
  • Updated the Netty network application framework library from 3.10.4 to 4.1.44.
  • Updated Log4j from version 1.2.14 to 2.10.
  • Fixed an issue that would cause an error in the log when disconnecting from GoAnywhere MFT.
  • Fixed an issue where UDP Ports where not getting closed after a transfer.
  • Fixed an issue that could cause Gateway to disconnect from GoAnywhere MFT if the Gateway UDP configuration was incorrect.

February 15, 2019 - Version 2.6.1

  • Added official support for the Azul Zulu JRE.
  • Updated the installer for Windows to ensure the path to executable on the service is quoted.
  • Updated the HTTPS load balancer to better persist the session during long transfers.

October 13, 2017 – Version 2.6.0

  • Rebranded GoAnywhere Gateway as a HelpSystems product.

April 13, 2017 – Version 2.4.0

  • Added new ‘AgentIP’ session persistence option for supporting GoAnywhere Agent connections through GoAnywhere Gateway.

November 22, 2016 – Version 2.3.0

  • Improved the licensing capabilities with the following features:
    • Self-service access to product licenses through the GoAnywhere Customer Portal at my.goanywhere.com.
    • Ability to refresh/update a license with a single command.
    • Allow the customer to evaluate optional features for an existing paid license.
    • More accurate server identification. This fixes an issue where Serial numbers could change if the JRE used by GoAnywhere Gateway was updated.
  • Added the ability to specify a Shared Secret value on Gateway configurations. This shared secret may be required by the Gateway server to authentication the MFT system.
  • Added the ability for IP whitelisting and blacklisting to occur at the Gateway level in the DMZ rather than on MFT only.
  • Added the ability to turn on SSL encryption on the Gateway configuration to protect the control channel's communication.
  • Fixed an issue where the GoFast UDP listeners were causing the graceful shutdown to hang.

March 10, 2016 – Version 2.2.0

  • Added support for GoFast accelerated file transfers through GoAnywhere Gateway.

December 3, 2015 – Version 2.1.1

  • Fixed an issue where explicitly setting the socket buffer size for passive FTP/S data connections could cause the performance to degrade in some networks.

February 10, 2013 – Version 2.1.0

  • Enhanced GoAnywhere Gateway to support being installed in an environment where connections from the private network go through a NAT firewall to access the DMZ.
  • Updated the default number of Max Threads setting to 2000. This affect new installs only.

May 15, 2013 – Version 2.0.1

  • Fixed an issue where persisted sessions were not cleaned up properly when a GoAnywhere Services control channel disconnected.

December 17, 2012 – Version 2.0.0

  • Enhanced GoAnywhere Gateway so it can be used as a load balancer in front of two or more installations of GoAnywhere Services. This provides greater scalability by allowing file transfer workloads to be distributed across multiple systems.
  • Added support to allow two or more installations of GoAnywhere Services to use the same proxy (listener) ports for handling client connections.
  • Added two load balancing algorithms which can be configured within the gateway.xml file in the installation directory. These algorithms determine how traffic is routed when multiple installations of GoAnywhere Services are connected to the same listener:
    • Round Robin algorithm will rotate client connections evenly across GoAnywhere Services installations. This is the preferred algorithm for FTP, SFTP and FTPS protocols.
    • IP-Based Session Persistence algorithm will also rotate client connections, but will keep traffic from the same IP flowing to the same GoAnywhere Services system for a period of time. This is the preferred algorithm for stateless protocols like HTTP/S.

October 2, 2012 – Version 1.2.0

  • Fixed an issue where passive ports for FTP/S were failing to timeout when clients requested passive data connections but did not use them. This fix requires GoAnywhere Services version 3.0.1 or higher.

October 21, 2011 – Version 1.1.1

  • Added a new option to customize the local address used by the forward proxy when establishing outbound connections.

July 20, 2011 – Version 1.1.0

  • Enhanced GoAnywhere Gateway so it can also be used as an outbound proxy server by GoAnywhere Director (version 3.6 and later) for FTP, FTPS, SFTP and SCP protocols.
  • Allow the routing of passive and active data connections (in addition to the control connections) when using FTP and FTPS protocols in GoAnywhere Services. GoAnywhere Services 2.1.0 or later is required to make use of this feature.
  • Fixed an issue where the information needed to obtain a new license was not available for review if the current license was expired.
  • Fixed an issue where a debug message was being logged stating a message had been received, when it was in fact being sent.

September 1, 2010 – Version 1.0.0

GoAnywhere Gateway is a new product from Linoma Software [now HelpSystems]. It acts as an enhanced reverse proxy that provides an additional layer of defense for your DMZ and Internal network. GoAnywhere Gateway integrates with GoAnywhere Services to provide a secure and managed environment for hosting and exchanging files.
  • No incoming ports need to be opened into the private (internal) network
  • No sensitive files, user credentials or service configurations are maintained/stored in the public (DMZ) network.
  • Supports FTP/s, SFTP and HTTP/s file transfer protocols
  • No special hardware components required; software-only solution
  • Installs to Windows, Linux, AIX, UNIX and Solaris operating systems

Learn More: DMZ Secure Gateways: Secret Weapons for Data Security