SecureFX(R) 7.3.7 (Official) -- February 25, 2016 Copyright (C) 1995-2016 VanDyke Software, Inc. All rights reserved. This file contains a 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 7.3.7 (Official) -- February 25, 2016 --------------------------------------------------------- Bug fixes: - SecureFX could crash if the transfer queue contained active transfer operations from multiple sessions and then another transfer was initiated by dragging a file to the transfer queue. - If the Session Manager had Auto Hide enabled and SecureFX was launched from a desktop shortcut that started SecureFX minimized, when SecureFX was restored and the Session Manager was displayed, it was very narrow. - If the configuration folder was located on a network drive or contained a large number of sessions, the Session Manager was slow. - When upgrading from a version of SecureFX prior to 5.0, saved passwords were not migrated to the new version. - Mac/Linux: When multiple sessions were selected in the Session Manager or Connect dialog, the right-click menu contained two items that were wrong. Changes: - Added a synchronize INI-file-only option "Transfer To Temporary File" that allows the use of .vs_temp files to be disabled. Changes in SecureFX 7.3.6 (Official) -- December 1, 2015 -------------------------------------------------------- Bug fixes: - The New Session wizard reported an error when an IPv6 address was entered as the hostname. - When the global option "Default transfer type" was set to "Prompt for type," the option "Use this type for all files" was enabled. - SFXCL: Server-to-server transfers did not use the specified destination path. - SSH2: SecureFX hung when attempting to connect to a session that used CAPI for public-key authentication if the personal store was empty. - Mac: SecureFX crashed when attempting to do public-key authentication with a certificate in a format not supported by SecureFX. - Mac: If a password for a session was saved in the OS X keychain and then the option to save to the keychain was turned off, when connecting to the session, the authentication prompt contained an incorrect password. - Mac: On OS X 10.11 (El Capitan), there were display issues with the San Francisco system font. Changes in SecureFX 7.3.5 (Official) -- September 10, 2015 ---------------------------------------------------------- Bug fixes: - SFTP: When downloading files from some remote systems (e.g., Globalscape), if SecureFX issued multiple parallel read requests, the transfer could fail to complete without reporting an error. - SFXCL: If SFXCL was run as SYSTEM, synchronize operations failed to open the local folder and reported the error "The parameter is incorrect." - SFXCL: If multiple instances of SFXCL were started, it could incorrectly report the error "Operation failed because the configuration passphrase is being entered or modified in another process." - Mac: In the Global Options dialog, in the File Transfer/SSL category, if the browse button was used to select a valid PFX file, the certificate was not used. Changes in SecureFX 7.3.4 (Official) -- June 16, 2015 ----------------------------------------------------- Changes: - SFTP: Added a session INI-file-only option "Disable Remote File System Watches" that can be used to prevent connections from attempting to establish file system watches on directories. This option can be used on systems behind firewalls, such as McAfee Firewall Enterprise. Bug fixes: - Server-to-server transfers failed if the source server's read buffer size was larger than the destination server's write buffer size. - When SecureCRT and SecureFX were integrated, if the configuration passphrase was changed in one application while the other application was running, the sensitive data could have been encrypted incorrectly. - The personal data folder could not be merged with the configuration folder if the personal data folder contained any empty session folders. - When the Session Manager was in autohide mode and a session was connected, if a menu was activated using the keyboard and dismissed by pressing ESC, and then the keyboard accelerator to display the Session Manager was pressed, the Session Manager gained focus but remained hidden. - FTP: Server-to-server transfers between two FTP sessions hung at the end of the transfer. - SFTP: Under certain circumstances, SecureFX could crash when attempting to do a server-to-server transfer. - SFXCL: Attempting to do a server-to-server transfer where the destination session did not exist caused a crash. - SFXCL: SFXCL could hang on server-to-server FTP transfers. - SFXCL: If the FTP server was restarted, transfers did not resume as expected. - Windows: PKCS11 authentication failed with FortiToken ePass2003. - Windows: CAPI authentication failed with the Fortinet FTK300 token. - Mac/Linux: In the Manage Agent Keys dialog, if all keys were removed and then the Remove button was pressed again, SecureFX crashed. - Mac/Linux: The Help contents, search, and glossary were not available. Changes in SecureFX 7.3.3 (Official) -- March 31, 2015 ------------------------------------------------------ New features: - Previous versions of SecureFX supported saving passwords and other sensitive data. In order to improve the security of this feature, SecureFX now allows a passphrase to be created the first time version 7.3.3 runs. This passphrase will be used to encrypt and decrypt sensitive data stored in the session database. Bug fixes: - SFTP: SecureFX crashed when attempting to connect to a Mikrotik network device. Changes in SecureFX 7.3.2 (Official) -- February 26, 2015 --------------------------------------------------------- Changes: - SSH2: When attempting to authenticate using a CAPI key or certficate with a smart card, if the card returns an error, SecureFX attempts to continue authentication, which allows authentication to succeed with certain smart cards, such as GoldKey. Bug fixes: - If a dependent session was used as the firewall for a session, SecureFX could hang when uploading a large file. - If a file on the local system was being written, it could not be uploaded to a remote system. - If autohide was on for the session manager, the most recently opened session was not selected when the session manager was shown again. - If the remote system was OS/400 MEM, file information was not displayed in the tree view. - SFTP: SecureFX could freeze or crash when attempting to do a synchronize operation where the remote system was a Serv-U SFTP server. - Mac/Linux: The crash reporter dialog did not show crash information for the most recent crash. Changes in SecureFX 7.3.1 (Official) -- December 4, 2014 -------------------------------------------------------- Changes: - In order to address the POODLE attack, SSL 3.0 is disabled by default. - SSH2: When using public-key authentication, if the .PUB file is not present, it is created automatically so that agent will work. Bug fixes: - SecureFX could hang when attempting to stop using a personal data folder. - Files were not displayed in the tree view when the remote side was OmniSwitch. - Mac: In the Global Options dialog, in the Sound category, SecureFX crashed when attempting to select a file. - Mac: Attempting to add a new file type in the Global Options dialog caused the error "Undefined error: 0". Changes in SecureFX 7.3 (Official) -- October 23, 2014 ------------------------------------------------------ Bug fixes: - SecureFX crashed when attempting display the information for an incorrectly formatted SSH host key. - Windows: Selecting the "Update Now" menu item did not reset the clock used to check for updates every 30 days. Changes in SecureFX 7.3 (Beta 5) -- October 2, 2014 --------------------------------------------------- Changes: - In order to prevent potential data loss, merging the personal data store with the configuration folder is only done if the session structure is exactly the same for both. Bug fixes: - The previously selected session was not remembered when the session manager was closed and re-opened. - Mac: The clear button in the session filter edit box was very small on Retina displays. Changes in SecureFX 7.3 (Beta 4) -- September 23, 2014 ------------------------------------------------------ New features: - Windows: 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: - Windows: Added the keyboard shortcut ALT+SHIFT+S to launch the Synchronize dialog. - Mac: Added the keyboard shortcut SHIFT+COMMAND+S to launch the Synchronize dialog. Bug fixes: - Mac: If the Connect dialog was used instead of the session manager, using the keyboard shortcut COMMAND+I to move focus to the session filter box caused SecureFX to crash. Changes in SecureFX 7.3 (Beta 3) -- September 9, 2014 ----------------------------------------------------- New features: - Added a search filter to the Connect dialog, which helps find sessions quickly, especially when a large number of sessions have been saved. - Added support for diffie-hellman-group-exchange-sha256 key-exchange algorithm. Changes: - SFTP: The modulus for the Diffie-Hellman key exchange algorithms can be set from 1024 to 8192. Bug fixes: - Saved passwords could be deleted inadvertently by pressing ENTER when focus was in the Password field of the Password Properties dialog. - When using the filter bar to search for sessions, the session tree did not return to the original state if the option "Save expanded folder state in connect dialog" was off. - If the remote connection was lost during PGP encryption of a file and the connection was reestablished, the transfer failed due to a file in use error. Changes in SecureFX 7.3 (Beta 2) -- August 26, 2014 --------------------------------------------------- Changes: - In the session manager, when text is entered in the filter bar, the first matching session gets selected. - Windows: In the session manager, the filter bar can be cleared by pressing the ESCAPE key or the "X" button. Bug fixes: - SecureFX crashed when the backspace key was used to go to the parent folder. - FTP: SecureFX incorrectly reported an error when attempting to connect to a session that used a USER type firewall. - After importing settings, the imported button bars were not loaded. - Mac: SecureFX crashed if focus was in the filter bar and SecureCRT was closed using CMD+Q. - Mac: On Mavericks (10.9), SecureFX could not open a file a second time using "Open With..." and TextEdit. - Mac: Attempting to convert a private key to OpenSSH format failed to export the key. - Mac: When sessions were tiled, pressing CMD+ENTER on a session in the session manager did not open the session properties dialog. - Linux: SecureFX crashed if the session manager was enabled and SecureCRT was closed using ALT+F4. - Mac/Linux: The Export Settings and Import Settings dialogs did not automatically scroll when the progress information was displayed. Changes in SecureFX 7.3 (Beta 1) -- August 7, 2014 -------------------------------------------------- New features: - Added support for exporting and importing SecureFX settings to and from XML, which makes it easier to copy settings from one machine to another. - Mac/Linux: Added a session manager that can be used in place of the modal Connect dialog. The session manager can be in a pane in the SecureFX window or can be an undocked modeless dialog. - Added a search filter to the session manager, which helps find sessions quickly, especially when a large number of sessions have been saved. - Added the ability to specify that PGP encryption should be used for file transfers, including synchronize operations. A third- party library such as GnuPG is required for this feature. - Added the ability to specify the substitution parameter %USERNAME% as a session username. - Added a new session option "Display Filenames using UTF-8 encoding" that specifies that files should always be displayed in UTF-8. - SFXCL: Added "resume" as a possible argument to the "Overwrite" option, which allows an interrupted transfer to be resumed. - Linux: SecureFX for Linux now includes the SFXCL command-line utility. Changes: - Added the ability to store keys larger than 2048 bits in agent. - Added the ability to generate keys larger than 2048 bits. - When connecting a session, if there's an agent key associated with the session, it is tried first. This can help prevent a session from failing to connect because the maximum number of authentication retries was exceeded. - The MD5 and SHA-1 fingerprints are now displayed in dialogs that show host key information. - The parallel transfers setting now applies to all transfers in SecureFX and SFXCL. Previously, the setting only applied to the transfer queue and synchronize operations. - The local path can now be specified as a UNC path. - Font information was added to the information stored in the personal data folder. Bug fixes: - SecureFX could crash if multiple sessions specified the same session as a firewall (i.e., jump host). - SecureFX did not upload the remote file when it was changed in certain editors, such as UltraEdit and Notepad++. - SFXCL: If multiple paths were specified for the /List command, a transfer operation was performed instead of a list operation. - Windows: SecureFX could crash when doing multiple large server- to-server transfers using SFTP. - Windows: Deleting the same session from multiple instances of SecureFX using the session manager could cause all the sessions to be deleted. - Windows: When using the session manager, if the default session was changed to include a username and a session was connected, SecureFX prompted for the username. - Mac/Linux: SecureFX could hang or cause 100% CPU usage when the file transfer protocol was changed. - Mac/Linux: If the posix directory was a symbolic link, it caused SecureFX to hang when attempting to open the Session Options dialog. - Mac/Linux: If SecureCRT and SecureFX were running and a change was made to the global or session options in one of the applications, the changes were not picked up by the other application. - Linux: Deleting the same session from multiple instances of SecureFX using the session manager could cause SecureFX to crash.