SecureFX(R) 8.3.4 (Official) -- July 12, 2018 Copyright (C) 1995-2018 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 SecureFX_README.txt (downloaded with this installation). Changes in SecureFX 8.3.4 (Official) -- July 12, 2018 ----------------------------------------------------- Bug fixes: - SecureFX could crash when disconnecting an SFTP session. - Linux: The SecureFX installer failed on Ubuntu 17. Changes in SecureFX 8.3.3 (Official) -- May 3, 2018 --------------------------------------------------- Bug fixes: - SecureFX crashed if an FTP session was disconnected after viewing the Properties dialog for a remote file. - Mac: If focus was in the Connect bar and text was entered causing the auto complete dropdown to be displayed, SecureFX crashed if it was closed using the red "X". - Mac: Remote edit would not upload files when changes were made without exiting the editor. Changes in SecureFX 8.3.2 (Official) -- February 8, 2018 -------------------------------------------------------- Bug fixes: - When using Quick Connect, if a firewall that was just created was specified, the firewall was not used when the session connected. - Extracting a public-key file from a private key failed with ECDSA keys that were created with ssh-keygen. - Mac: Remote edit would not upload files when changes were made without exiting the editor. - If an illegal character was used in the name of a synchronize session, the synchronize session was not written to disk. Synchronization session names are now validated to ensure that they do not contain illegal characters. Changes in SecureFX 8.3.1 (Official) -- December 7, 2017 -------------------------------------------------------- Bug fixes: - SecureFX was not able to correctly parse a URI with two '@' characters (e.g., user@domain@host). - It was not possible to cancel transfers from the transfer tab using the keyboard. - Mac: When the current user didn't have permission to write on the "/cores" directory, the message SecureFX displayed at startup incorrectly stated that 8.3 official was an internal build. - Windows: SecureFX could not be installed on Windows Server 2008. - Windows: The 32-bit version of SecureFX was not able to transfer a 5 GB or larger file using SCP. - Windows: If the Connect bar was moved to the menu bar using the Customize dialog, auto complete in the Connect bar no longer worked. - Windows: Many dialogs had display issues on high-DPI monitors when the system was scaled to 125% or 175%. - Mac: SecureFX could crash if a folder contained a lot of symbolic links and the folder was collapsed or the arrow keys were used to navigate in the folder tree view. Changes in SecureFX 8.3 (Official) -- November 9, 2017 ------------------------------------------------------ No changes. Changes in SecureFX 8.3 (Beta 4) -- November 2, 2017 ---------------------------------------------------- Change: - Added icons for many menu items, which are displayed in the menus on Windows and can be used to customize the toolbar on Windows and Mac. Bug fixes: - SecureFX could crash when a parallel transfer upload was cancelled. - When SecureCRT and SecureFX were integrated and the "Cache session password" option was on, if quick connect was used to connect to an SSH2 host that used password authentication and then SecureFX was launched, automatically connecting to the same SSH2 host, the password had to be re-entered. - Windows: SecureFX could crash when the computer woke from Sleep or Hibernate mode. - Mac: SecureFX crashed if COMMAND+Q was pressed during a large file transfer, the transfer in progress warning dialog was dismissed, and COMMAND+Q was pressed again. - Linux: On high-DPI monitors, text and fields in some dialogs were cut off. Changes in SecureFX 8.3 (Beta 3) -- October 12, 2017 ---------------------------------------------------- Bug fixes: - SFXCL returned a success code when a command failed to run because the evaluation license had expired. - The Move up, Move down, and Play (sound) icons in dialogs did not display correctly on high-DPI monitors. - Windows: SecureFX crashed in the Windows 10 Creators Update when a smart card (PIV/CAC) was used. - Mac: The menu bar contained two Help menus. - Linux: The Table of Contents was missing from the online Help. Changes in SecureFX 8.3 (Beta 2) -- October 3, 2017 --------------------------------------------------- Bug fix: - SCP sessions did not work correctly when the remote system was a Cisco Nexus device. Changes in SecureFX 8.3 (Beta 1) -- September 21, 2017 ------------------------------------------------------ New features: - Improved the performance of synchronization operations involving large numbers of files and folders. - Improved the performance of listing large local directories. - SFXCL now returns the following exit codes: 0 (SUCCESS) 100 (Network error) 200 (Source file system error) 300 (Target file system error) 400 (General failures) - Added autocomplete to the Connect bar in the toolbar, which makes finding and connecting to saved sessions easier. - Multiple sessions can be dragged and dropped or copied and pasted in the Session Manager and Connect dialog. - A new global option "Sort folders at top" forces the folders always to be sorted at the top of the local and remote windows regardless of which column is used for sorting and whether the order is ascending or descending. This option is on by default for new installations. - SSH2: Added support for the ChaCha20/Poly1305 cipher. - SSH2: Added support for the AES-GCM cipher. - SSH2: Added support for the UMAC-128 MAC algorithm. - Added the ability to use OpenSSH certificates for authenticating SFTP sessions. - SSH2: Added a new session option "Use a separate transport for every connection," which establishes a new SSH2 transport for every parallel SFTP transfer. - SFXCL: Added a new option /ReconnectDelay, which allows the number of seconds between losing a connection and the initial reconnect attempt to be specified. - Windows: Added an Administrative Policy option to disconnect sessions authenticated using CAPI/PKCS#11 when the corresponding smart card is removed. - Mac: Added an "Update Now" menu item to see if a new version of SecureFX is available and if there is, clicking a button downloads and installs it. Changes: - Filtered searches in the Session Manager and Connect dialog could be very slow when the session database contained thousands of sessions. - In the Transfer queue, when the filename or destination is a remote system, the hostname is prepended. - The option for displaying hidden files in the local window can be toggled from the View menu. - If the global option "Show Session Manager or Connect dialog on startup" is set, the Session Manager is displayed when SecureFX starts. Previously, only the Connect dialog honored this option. - SSH2: Modified the default authentication order to be PublicKey, Keyboard Interactive, Password, and GSSAPI. This only affects new installations. - The default session filter delay has been changed from 500 milliseconds to 250 milliseconds. This only affects new installations. - Mac: For new installations, the global option "Use keychain" is off by default. - Up to 16 sessions can be included on the recent session list. - SSH2: If a session is using public-key authentication and the key file has not been specified, the user is no longer prompted to specify the file. - SSH2: When importing an SSH2 host key, if it's possible to extract the hostname, IP address, and port from the filename, those values will be used as the default values. Otherwise, the default value for port will be set to 22 and the other values will be left blank. - SSH2: Pressing the SHIFT key in the New Host Key dialog allows a host key to be saved once. - SSH2: In the dialogs that prompt to accept the host key, the SHA-2 fingerprint is also displayed in base64. - In the View Host Key dialog, SHA-2 fingerprints are displayed in base64 in addition to hexadecimal. - When being prompted to accept an SSH2 host key, the fingerprints are now shown in a separate dialog. - SSH2: The trace output shows the SHA-2 host key fingerprint as base64 in addition to hexadecimal. - The username used for authentication is now logged in the trace output. - SecureFX uses a templated path, which gets modified to an appropriate path on each platform, for the global option "Log File V2". - If SecureFX is launched using the -F command-line parameter or is on a USB drive, the actual configuration path being used is shown in the Global Options dialog. Bug fixes: - In the New Session wizard and the Quick Connect dialog, once a session was selected as the Firewall, "Select Session..." was no longer in the Firewall dropdown list. - When uploading a file to a Cisco iOS device, a prompt was displayed if the file did not exist in the target folder. - File transfers to a Cisco ASR9K router using SCP failed because SecureFX sent an extra "cd" command, which made the wrong directory the current directory. - The transfer queue displayed "Could not retrieve error text for error code 0xe000001c" when an upload failed due to a disk space error. - A session that contained spaces could not be connected from the Connect bar using the /S flag. - Windows: If the Connect bar was showing a dropdown list, pressing ALT+Q displayed the Quick Connect dialog, but did not put focus there. - Windows: On high-DPI monitors, the EULA dialog in the installer did not display correctly. - Linux: In Ubuntu 16, toolbar icons and dialog fonts were not displayed properly with high-DPI settings.