SecureFX(R) 9.6 (Official) -- November 19, 2024 Copyright (C) 1995-2024 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.6 (Official) -- November 19, 2024 ------------------------------------------------------- No changes. Changes in SecureFX 9.6 (Beta 5) -- November 12, 2024 ----------------------------------------------------- Bug Fixes: - When importing FTPS or HTTPS sessions, the FTPS/HTTPS-specific session options were not imported correctly. - When firewall configurations were included in an XML file import, existing firewalls with the same name were not updated with the new settings. - Windows: When using a legacy theme (e.g., Shaded), certain toolbar buttons may have used the incorrect icons. Changes in SecureFX 9.6 (Beta 4) -- October 24, 2024 ---------------------------------------------------- Changes: - Mac/Linux: Proxy commands specified in firewalls will use the user's shell environment. - Mac: When switching the window format from tabs to tiles, an icon is no longer shown on the tiled window title bar. Changes in SecureFX 9.6 (Beta 3) -- October 1, 2024 --------------------------------------------------- Changes: - When using a personal data folder, if the configuration path is changed in the Global Options dialog, the personal data folder will be updated to match only if it has the same path. - The Bookmarks address bar button now displays a popup tooltip and a status bar tip. Bug Fixes: - If TLS certificate validation was disabled, certificate revocation checking may have still been performed. - Mac/Linux: When the "Bandwidth limit" option was configured, the actual bandwidth limit imposed was much lower than the limit set. - Mac: When using a PKCS #11 library to access certificates on a smart card, the Select Certificate dialog did not display the certificates on the smart card. - Mac: PKCS #11 provider libraries with a .so extension were not selectable from the Public Key Properties dialog. Changes in SecureFX 9.6 (Beta 2) -- August 28, 2024 --------------------------------------------------- Bug Fixes: - When connecting to an AWS S3 host, certain regions (e.g., us-isob-east-1) failed to connect. - When selecting a certificate using PKCS #11 in the Public Key Properties dialog, the "Get username from certificate" option was unselectable. - Windows/Linux: When running synchronization operations in SFXCL, the values specified for the "Retry Attempts" and "Retry Delay" options in the Global.ini file were ignored. Changes in SecureFX 9.6 (Beta 1) -- August 15, 2024 --------------------------------------------------- New Features: - Added a button to the address bar that makes it easier to access bookmarks. - Added SCP support for NetMRI devices. - Added support for POSIX renames (posix-rename@openssh.com). - Added the ability to accept OpenSSH trusted certificates as host keys. - Added support for SSH private keys encrypted with the AES-256-CBC cipher. - Initial filters can be specified for a session's local and remote directories. - Specific folders and sessions can be selected and exported to an XML file. - Added the ability to prevent sensitive data such as passwords and usernames from being included in an XML export. - Added the ability to include the sensitive configuration data contained in the personal data folder when doing an XML export. - Added the ability to change the hostname (or IP address) for multiple sessions at the same time. - SFXCL: Added wildcard support to file listings (/LIST). - SFXCL: On Windows and Linux, added support for /LIST with local file paths. - Mac/Linux: Added a new Firewall type "Proxy command" which allows a local proxy command to be run when connecting to a remote server. - Linux: Added support for Ubuntu 24.04 LTS. - Linux: The system appearance Light or Dark setting is honored by the SecureFX application window. Changes: - For new configurations, the default value for the receive and send buffers is "Use system default size". - SecureFX no longer puts quotes around the comment when generating keys. - For XML exports, the hostkey database is only included by default when "Global Options" is selected. - Public-key information is now stored in the personal data folder if it is being used. - When enabling a personal data store, the personal data folder path must now be an empty directory. - When using a personal data store, the personal data folder path will update to match any changes made to the public configuration folder. - The Hostname can now be modified when editing multiple sessions. - The Manage Agent Keys dialog now supports multi-selection and bulk removal of keys. - Added a global INI-file-only option "SFXCL Honor Unescaped Wildcards" to set SFXCL to interpret unescaped '?' characters as wildcards. - Windows: The installer is now compliant with Microsoft guidelines for Single Package Authoring (dual-purpose package), which allows per-machine and per-user installations. - Windows: For new installations, the taskbar thumbnail preview now shows a single thumbnail of the application window. - Windows: When adding a new credential, the Public Key Properties dialog can now be opened before a credential title and username have been specified. - Mac: The correct icon is now shown in the File Types page in the Global Options dialog. - Mac: Title bars, toolbars, and status bars no longer have a gradient style. Bugs Fixes: - When connecting to an AWS S3 host and the "us-gov-*" region was specified, the connection failed. - When using PGP to decrypt downloaded files, PGP armored files (.asc extension) were not decrypted. - When the SecureFX log file was changed to include an environment variable (e.g., %USERPROFILE%), the environment variable was not expanded and a folder with the name of the variable was created. - When importing sessions from an XML file, the session options not specified in the XML file did not inherit from the Default session as expected. - When the "Show Session Manager or Connect dialog on startup" option was enabled and there were no saved sessions, the Session Manager or Connect dialog were not shown at startup. - When using OpenSSL for TLS connections (the default on macOS and Linux), the available client-side TLS protocols were not logged correctly. - When using the New Session wizard to create a session, the firewall dropdown listed each configured firewall twice. - When prompted with certain SSH1/SSH2 host key acceptance dialogs, the text on the dialog may have been malformatted. - When the license data copied to the clipboard stripped the newlines (i.e., license data was on a single line), the License wizard was not been able to parse the data. - Windows: When the VANDYKE_SSH_AUTH_SOCK environment variable was used to specify a different SSH agent to use, SecureFX did not honor the setting. - Windows: When a SecureFX window was shared within a Microsoft Teams meeting, certain actions could cause the window to appear frozen to the meeting attendants. - Windows: When the Enter key was pressed to connect to a session or host from the Connect Bar, a bell sound was unexpectedly played. - Windows: With FIPS mode enabled, attempting to change an RSA private-key passphrase failed. - Windows: The SecureFX application window could have been displayed off screen if the system display settings were changed. - Windows: If the system text size was increased, the text displayed on various dialogs was not scaled as expected. - Windows: When navigating the Firewall selection dropdown via the keyboard, when the "Select Session..." option was highlighted, the Select Session dialog was automatically opened. - Windows: On some dialogs, the label was not displayed when the mouse hovered over a button. - Windows: Importing from an XML file failed silently if an imported session's name contained illegal characters. - Windows: When launching the Connect dialog from a docked SecureCRT taskbar icon, then choosing to open a session in SecureFX, both SecureCRT and SecureFX opened. - Windows: When using the OpenSSH agent, if an error occurred when a key was added to the agent, the error message may not have been displayed as expected. - Windows: When focus was in the Connect Bar and the Enter key was pressed without entering a hostname or session, a connection was attempted using the "" hint text as the hostname. - Windows: When SecureCRT and SecureFX were integrated and the terminal protocol was changed to one that does not allow a file transfer protocol to be set, the file transfer pages may not have been hidden. - Windows: On Windows 11, the application window did not have rounded corners when the "VS2013 Blue", "VS2013 Dark", or "Office 2013" display theme was selected. - Mac: When updating the applications using "Update Now", if elevating to an administrator account was required, the installation of the new version may have failed. - Mac: When the system color mode changed from Light to Dark or Dark to Light, the color of some items in the Global and Session options dialogs did not update. - Mac: When SecureFX was launched for the first time with a new configuration, both the Session Manager and Quick Connect dialog were displayed. This resulted in focus being placed in the Quick Connect dialog with no visible cursor. - Mac: The SecureFX icon appeared blurry on some Retina displays when using Command+Tab to switch applications. - Mac/Linux: When connecting to a session that had an IP address specified for the hostname, an unnecessary name lookup was performed on the IP, which could result in the connection failing. - Mac/Linux: When opening SecureFX from a connected SecureCRT session tab, the session did not open after SecureFX launched. - Linux: When SFXCL was exiting from an operation, a crash could have occurred. - Linux: When using SFXCL for an FTPS connection, TLS-related log messages may not have been displayed as expected. - Linux: The Help button in the Connect dialog could not be pressed.