SecureFX(R) 9.0 (Beta) -- October 20, 2020 Copyright (C) 1995-2020 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 9.0 (Beta 2) -- October 20, 2020 ---------------------------------------------------- Bug Fixes: - When exporting the configuration to a file, if a folder name was specified instead of a filename, the export file was created using the folder name and the folder itself was renamed with a ".bak" extension. - When SecureCRT and SecureFX were installed as a combined installation (integrated) and the SecureFX Session Manager option "Show Terminal Sessions" was off, SecureCRT local shell sessions were still shown. - Windows: If some parent path component of the local window directory was not accessible to the user, the local window could not be interacted with and the main window could not be closed. Changes in SecureFX 9.0 (Beta 1) -- September 24, 2020 ------------------------------------------------------ New Features: - Added support for transferring files to and from Amazon S3. - Added the ability to specify public/private keys to load into SSH2 agent when SecureFX starts. - Added support for the rsa-sha2-256 and rsa-sha2-512 public-key algorithms (RFC 8332). - Added an option to have transferred files be timestamped by the destination server. - Added a global option to automatically remove files from the transfer queue after the transfer is finished. - Added the ability to use wildcard characters "*" and "?" in the Session Manager filter box. - SSH2: The host-key algorithms can now be specified and ordered in the Session Options dialog. - Windows: Added an administrative option that disallows a blank configuration passphrase. Changes: - SSH2: Removed support for several weak ciphers (Blowfish and RC4) and MACs (SHA1-96, MD5, and MD5-96). - HTTPS: When connecting to a VShell HTTPS server, the home directory defaults to the directory sent by VShell in a cookie. - When connecting to a ProFTPD mod_sftp server, SFTP version 3 is used by default. - Added the ability to reorder sessions in the Auto Session list. - In the Manage Agent Keys dialog, the fingerprint is displayed as SHA-2. - When IPv6 hostnames are displayed in tabs or the application title bar, the colons (":") are no longer replaced with underscores ("_"). - In the Global Options dialog, in the SSH Host Keys category, the Hostname and Port columns now sort logically instead of alphabetically. Bug Fixes: - SCP: When connected to a server that does not support a secondary channel open request, copying a file from one folder to another on the remote system could result in a hang. - Parallel transfers to a Microsoft IIS HTTP/S server could hang if the transfers were initiated by dragging multiple files to the remote session. - HTTPS: If a file or folder name contained certain characters (e.g., "#" or "%"), HTTPS operations on that file or folder failed. - HTTPS: When connecting to an HTTPS (WebDAV) server, if a failed authentication attempt was immediately followed with a successful attempt, the connection still failed. - HTTPS: When uploading a file to a restricted directory that would have resulted in an access denied error, the file transfer may have been reported as successful. - When attempting to connect to an ownCloud WebDav server, the initial connection and/or traversing the file system could have failed. - When the "Confirm overwrite" option was enabled, file uploads to the slimFTPd server could have failed. - Uploading a zero-byte file to certain FTPS servers could fail with a "Network connection does not exist" error. - If the "Disable directory tree detection" option was enabled, file or folder delete operations could fail. - When connecting to an FTP server on a Windows Embedded Compact (Windows CE) system, SecureFX did not auto-detect the operating system as Windows NT. - When transferring files to certain servers, SecureFX and SFXCL may not have used the ideal number of buffers, resulting in slower transfer speeds. - When connected to a Microsoft IIS HTTPS server, the root "/" directory may have been repeatedly displayed in the tree view. - When the "Display the log view" option was toggled while there were connected sessions, the change to the option was not saved or applied to the sessions. - Windows: If the internet connection was disconnected while downloading an available update via "Update Now...", the VanDykeUpdate application could crash. - Windows: When using CAPI to access a certificate located on a smart card and the CAPI store contained multiple certificates, there could be a delay before being prompted for the smart card pin. - Windows: On high DPI monitors with a large scaling factor set, text displayed on the Keyboard Interactive authentication prompt could have been cut off.