Version 5.6.2

  • Added the ability to support SMB version 2, 3, and 3.1.1 which adds additional security to SMB Network Shares.
  • Enhanced the GACMD action to Add SSH Keys to no longer require a password for SSH private keys.
  • Updated the ICAP connection to send case-sensitive HTTP headers which allows GoAnywhere MFT to properly communicate with Sophos SAVDI ICAP interface.
  • Updated the validation for SSH Tasks to provide a proper message when validating keys while using KMS and file based keys.
  • Updated the Web User's When File Exists preference to render correctly when an Admin User made changes to the Web User Configuration.
  • Updated the Web Client Applet to be signed with the new HelpSystems code signing certificate. The applet signature is now valid until 2020.
  • Upgraded the JSch library from 0.1.53 to 0.1.54. This version fixes an issue where file data could become corrupt during an SFTP Put action to certain servers when using stronger HMAC algorithms.
  • Removed an unnecessary scroll bar on the project designer file choosers for various protocols.
  • Fixed an issue where Resources connecting to Azure do not work properly when GoAnywhere MFT is running on Linux, Unix, and IBM i systems.
  • Fixed an issue where creating a directory on an Azure file system would fail with a timeout error.
  • Fixed an issue where FTPS Tasks and Resources would fail to trust the target server when using client certificate authentication and the server certificate fields are left blank. This issue was introduced in 5.6.0.
  • Fixed an issue where importing a PGP key into a key vault would fail if the key does not contain preferences for encryption and signature algorithms.
  • Fixed the ICAP task to properly read source files from an encrypted folder.
  • Fixed an issue where switching databases could reset certain configuration for two-factor authentication to the default values.
  • Fixed an incorrect validation message when using GACMD to remove and SSH private key that does not exist.
  • Fixed an issue where the SFTP server would not close sessions promptly when a client disconnects, which, depending on the number of active sessions allowed, resulted in a rejecting subsequent connections. This issue was introduced in 5.6.0