SecureFX(R) 8.0.4 (Official) -- December 6, 2016 Copyright (C) 1995-2016 VanDyke Software, Inc. All rights reserved. This file contains the SecureFX product history. It includes lists of new features, changes, and bug fixes sorted by release. For a product description, installation notes, registration information, and contact information, please refer to Readme.txt (downloaded with this installation). Changes in SecureFX 8.0.4 (Official) -- December 6, 2016 -------------------------------------------------------- Bug fixes: - When the session database contained several folders, if the settings were exported and then imported into an empty configuration, the folders were not in alphabetical order. - The Session Manager and Connect dialog showed the expansion icon on an empty folder if the folder previously contained sessions. - SSH2: SecureFX crashed when attempting to use the ECSA certificate from a Yubikey smart card. - SSH2: SecureFX reported an error when attempting to connect to a Cisco device that used the ident string "SSH-2.99-Cisco-1.25". - Windows: On a high-DPI monitor scaled to 150%, some of the controls on the Keyboard Interactive dialog were cut off. - Windows: The menu font in SecureFX was different from SecureCRT's. - Mac: If system accessibility options were on, SecureCRT could crash shortly after starting or waking from sleep. - Mac: Progress dialogs were displayed as a white box and could not be dismissed. - Mac/Linux: If all views, including the Local view, were closed and CTRL+TAB was pressed in the client area, SecureFX crashed. Changes in SecureFX 8.0.3 (Official) -- September 8, 2016 --------------------------------------------------------- Changes: - Mac: It is now possible to use a read-only configuration folder. Note: The configuration folder must be writable in order to enter the license data for SecureFX. Bug fixes: - SecureFX crashed when attempting to export settings that contained a session with a blank name. - SecureFX/SFXCL did not wait to receive the 221 response from the server after sending a QUIT, which could result in the control connection not being closed cleanly. - Windows: When toggling between new and legacy display themes, SecureFX could get in a state where the application toolbar contained the new icons and the menus contained the legacy icons or vice versa. - Mac: SecureFX could crash when it was launched from SecureCRT. Changes in SecureFX 8.0.2 (Official) -- June 14, 2016 ----------------------------------------------------- Bug fixes: - Mac: SecureFX crashed when attempting to create a session with a name containing Norwegian characters. Changes in SecureFX 8.0.1 (Official) -- April 26, 2016 ------------------------------------------------------ Changes: - Pressing ALT+M will open the Session Manager if it's hidden. - Pressing ALT+I will display the Session Manager if it's hidden and put focus in the filter bar. - Windows: SecureFX now uses the proper default action (Open or Edit) associated with file types in the system settings in order to work better with editors such as EmEditor. Bug fixes: - The fallback mechanism for public-key authentication did not work correctly and authentication failed rather than prompting for the username and public key. - When connecting to multiple sessions, the Local window was moved to a different tab group. - If SecureFX did not open any local or remote windows on startup and auto-hide was on for the Session Manager, the Session Manager stayed open. - Fixed a memory leak that occurred when ECDSA keys were used. - Mac/Linux: SecureFX crashed when attempting to use the Public Key Assistant. - Mac: Pressing ALT+M or ALT+G did not cause focus to change to the appropriate window (Session Manager or Transfer Queue, respectively). - Mac: If auto-hide was on for the Session Manager, pressing COMMAND+I did not move focus from the session tree to the session filter box. Changes in SecureFX 8.0 (Official) -- March 31, 2016 ---------------------------------------------------- Bug fixes: - SFXCL: When multiple SFXCL processes were launched simultaneously, SFXCL could prompt for a configuration passphrase even when no passphrase was used. - Mac: In the Session Manager and Connect dialog, it was not possible to select multiple sessions using COMMAND+. Changes in SecureFX 8.0 (Beta 5) -- March 22, 2016 -------------------------------------------------- Bug fixes: - If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, settings could not be saved in the personal data folder even though it was writable. - If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, attempting to merge the configuration data failed and the personal data was deleted. Changes in SecureFX 8.0 (Beta 4) -- March 10, 2016 -------------------------------------------------- New feature: - When setting up a synchronize operation, the remote folder can be browsed. Changes: - The Session Manager's "auto hide" option is on by default. - Windows: The mouse scroll wheel can be used when hovering over a UI element such as the list view or tree view without having to click first. Bug fixes: - Mac: SecureFX failed to start if the configuration contained an invalid log path. Changes in SecureFX 8.0 (Beta 3) -- February 18, 2016 ----------------------------------------------------- No changes. Changes in SecureFX 8.0 (Beta 2) -- February 9, 2016 ---------------------------------------------------- Changes: - Added the ability to disable scheduled tasks. Bug fixes: - When running an FTPS synchronization operation with a lot of remote files, the operation eventually failed with a "Connection terminated abnormally" error during a SIZE command. - An error string was displayed in the "Files of Type" field in the Select File to Upload dialog. Changes in SecureFX 8.0 (Beta 1) -- January 28, 2016 ---------------------------------------------------- New features: - Windows: Added the ability to schedule transfer and synchronize operations. The frequency can be once, daily, weekly, or monthly and SecureFX does not need to be running. - Windows: The user interface has new themes and new toolbar icons. - Windows: Updated the icons used in the remote view. - Added the ability to create a file on a remote system. - Added the ability to use and generate ECDSA (RFC 5656) and Ed25519 keys. - Added the ability to generate keys in the new OpenSSH format. - SSH2: PuTTY PPK keys can be used for public-key authentication. - SSH2: On Windows, enhanced public-key authentication to allow a public key to be specified from the CAPI or PKCS #11 store. - SSH2: On Windows, public keys can be exported in OpenSSH format and can be exported from PKCS #11. - SSH2: On Windows, added support for X.509 authentication using the x509v3-ssh-rsa and x509v3-ssh-dss algorithms as specified in RFC 6187. - SSH2: On Windows, certificates can be used as a raw key for public-key authentication. - SSH2: On Windows, X.509 v3 keys can be added to the SSH agent. Changes: - The ability to use a session as a firewall has been added to the Quick Connect dialog and the Session wizard. - Quick Connect sessions that are saved are put in the current folder in the Session Manager. - ID numbers shown in the log file for transfer, synchronize, and file operations are now unique. - The format of some log messages was changed as shown below: - "Session established for synchronize with " changed to "Operation established for synchronize with ". - "Synchronize(): sfxcl version ()" changed to "sfxcl version ()". - "Session established for session " changed to "Session window established for session ". - "Session established for address
" changed to "Session window established for address
". - "Session(00000000): sfxcl version ()" changed to "sfxcl version ()". - Changed the SSL GUI protocol names to "FTP/TLS (implicit)" and "FTP/TLS (explicit)" to reflect that TLS is supported. - Added "Contact Support" to the Help menu. - SSH2: If host key authentication fails with the ssh-dss algorithm, the ssh-rsa algorithm is preferred on subsequent attempts to reconnect the session. - SSH2: It's now possible to specify the minimum group exchange prime size in the Session Options dialog. - SSH2: The "diffie-hellman" key exchange algorithm is off for the default session. This change only affects new installations. - SSH2: SHA-1 and SHA-2 fingerprints are displayed for public keys in addition to MD5. - SSH2: In all places where the host key fingerprint is displayed, the SHA-2 fingerprint is also displayed. - SFXCL: Host key messages are now logged. - SFXCL: When the remote server is WS_FTP and the protocol is SFTP, trailing slashes are stripped from paths. - Windows: If the administrative policy "Enable Check For Updates" is set to false, "Update Now" is not allowed. Bug fixes: - Attempting to delete a session without a name caused every session in the session database to be deleted. - SecureFX could become unresponsive when settings were being imported or exported, especially when the configuration was large (e.g., lots of sessions). - SecureFX could not connect to an FTPS server that requested a client certificate without specifying a client certificate, which is allowed by SSL and TLS. - SFTP: If a binary file was transferred to a Globalscape server with compression set to zlib, the file could be corrupted. - SFTP: Files could be corrupted when multiple files were downloaded from an SFTP server if the maximum number of parallel transfers was set to a value larger than 1 and the transfer queue was being used. - SFTP: SecureFX did not work with MikroTik routers running RouterOS. - SSH2: If the host key database was on an offline cached network drive, SecureFX was not able to save new host keys. - SSH2: The cached session password was not updated after a password change was forced by the remote system. - SFXCL: If multiple files were transferred and one or more files failed to transfer, but one or more files transferred successfully, SFXCL returned a success exit code. - Windows: When the session database contained folders and one of those folders was deleted in the Session Manager, if a session was created using the Quick Connect dialog, the session was not saved in the selected folder and any expanded folders were collapsed. - Windows: On high-DPI monitors with scaling enabled, folders in the Session Manager and local and remote windows could not be expanded or collapsed. - Mac/Linux: The Session Manager could not be docked by double- clicking its title bar. - Mac/Linux: If SecureCRT and SecureFX were installed and the file types for SecureFX were changed in SecureCRT, the changes were not propagated to SecureFX.