SecureFX® 2.2.10 (Official) -- May 5, 2005 Copyright © 1995-2005 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 2.2.10 (Official) -- May 5, 2005 ---------------------------------------------------- Bug fixes: - On MVS servers, large partitioned data sets (PDS) were not displayed correctly. - SFXCL was not correctly reporting the number of files transferred in the summary output. Changes in SecureFX 2.2.9 (Official) -- February 3, 2005 -------------------------------------------------------- Changes: - At the end of a file transfer, SecureFX prints out a summary of the number of attempted file transfers, the number of successful transfers, and the names and error codes for any files that may have failed to be transferred. Bug fixes: - When SFTP version 4 was used, the text transfer flag was not being set. - If the folder tree view was collapsed and then expanded, the hard drives were no longer displayed. Changes in SecureFX 2.2.8 (Official) -- October 26, 2004 -------------------------------------------------------- Bug fixes: - After opening a Flash MX 2004 Pro file from within the local SecureFX window, SecureFX crashed if it was closed while the document was still open. - On VMS servers that use lowercase .dir for directory entries, directories were missing from the file listing. Changes in SecureFX 2.2.7 (Official) -- August 19, 2004 ------------------------------------------------------- Bug fixes: - When the Folder Tree was not being displayed, pressing the Tab key caused SecureFX to crash. - The file download failure error dialog did not include the filename. Changes in SecureFX 2.2.6 (Official) -- June 29, 2004 ----------------------------------------------------- Bug fixes: - SecureFX crashed when uploading a file through a SOCKS 5 proxy. - For remote files, the file size was incorrectly displayed for files larger than 4 gigabytes. - SecureFX was unable to parse directory listings from Sterling Commerce's Secure FTP. - SSH2: When prompted to accept a new host key, canceling went into a loop instead of exiting. Changes in SecureFX 2.2.5 (Official) -- May 20, 2004 ---------------------------------------------------- Changes: - SecureFX only sends the request for multi-roots if the SFTP version is greater than 3 or the server is VShell. - The authentication method can be selected from the Quick Connect dialog. Bug fixes: - A Rename operation on a local file or folder could have been interrupted by the automatic directory refresh. - If the local window was minimized and SecureFX was restarted, the local window would be minimized in a different location and sometimes hidden. - SecureFX went into an infinite loop when VShell placed the user in a root folder that was not readable. Changes in SecureFX 2.2.4 (Official) -- April 13, 2004 ------------------------------------------------------ Changes: - When the Properties dialog is opened, the Attributes field has focus. Bug fixes: - For new installations of SecureFX, the prepopulated session database was not being moved to the proper location during installation. - Files on a VMS server could not be edited remotely using "Open" or "Open with". - SSH2: When the remote identifier string was "SSH-2.0-Sun_SSH_1.0", SecureFX disconnected on a key re-exchange attempt. Changes in SecureFX 2.2.3 (Official) -- March 18, 2004 ------------------------------------------------------ Changes: - The authentication method can now be selected in the Quick Connect dialog. Bug fixes: - SecureFX crashed when a multiple file transfer was resumed and the file or folder being transferred was on the Windows desktop. - SSH2: The built-in authentication agent did not preserve the filename comment. Changes in SecureFX 2.2.2 (Official) -- February 12, 2004 --------------------------------------------------------- Bug fixes: - SecureFX crashed if any file attribute was more than 80 characters long. - Pressing Shift+F10 now displays the context menu. - SSH2: The "Auto Detect" SSH Server option did not work correctly with DataFellows 2.0.13 servers. - SSH2: SecureFX crashed when the remote host key was larger than 2048 bits. - SFTP: If an SFTP directory entry came back from the SSH2 server missing the size, permission, or time attributes, SecureFX would not list the entry. Changes in SecureFX 2.2.1 (Official) -- January 15, 2004 -------------------------------------------------------- Bug fixes: - Selecting text in the Log View window pane and pressing CTRL+C sometimes caused an access violation error. - Launching SecureFX under Windows 95 resulted in the following error: "Missing File WS2_32.DLL". Changes in SecureFX 2.2 (Official) -- December 4, 2003 ------------------------------------------------------ Bug fixes: - When using FTP over SSH2, SecureFX crashed if a transfer was interrupted and the reconnect was cancelled. - SFXCL could crash when CTRL+C was pressed more than once during connection or during an upload. Changes in SecureFX 2.2 (Beta 5) -- November 25, 2003 ----------------------------------------------------- Bug fixes: - For SFTP transfers, SecureFX issued read requests of 16K, which not all SFTP servers support. - When resuming SFTP ASCII downloads, the total progress meter showed an incorrect value. - For FTP over SSH2 sessions, SecureFX crashed when cancelling a transfer. - SecureFX produced an "Out of memory" error when resuming a transfer after upgrading to SecureFX 2.2 from any previous version. - SFXCL prompted for the password even when it was specified in the URL source, destination, or target. Changes in SecureFX 2.2 (Beta 4) -- November 13, 2003 ----------------------------------------------------- New features: - The location of the session database can be specified on the command line using /F. - Ability to rename files with SFXCL using the /RENAME flag. Bug fixes: - For resumed transfers, the transfer progress dialog sometimes showed incorrect information. - When a file was being overwritten and the transfer was interrupted, the transfer started over rather than resuming. - For FTP over SSH2 sessions, when anything other than Password was specified for the secondary authentication in the Session Options dialog, the primary authentication was forced to Password. - For SSH2 connections, SecureFX could crash when deleting a folder with many files while transferring a large file. Changes in SecureFX 2.2 (Beta 3) -- October 9, 2003 --------------------------------------------------- Changes: - For SSH2 connections that use GSSAPI authentication, the option "Enable deprecated GSSAPI" can be set on the SSH2 page of the Global Options dialog. Because most servers do not yet support GSSAPI with MIC, this option is on by default. - For SSH2 connections that use GSSAPI authentication, added an "Auto Detect" method, which is the default. "Auto Detect" selects the correct method during authentication. - For SSH2 connections, if public key authentication is used, but no identity file is specified, SecureFX prompts for the file and now saves it as the global identity file rather than the session identity file. - SecureFX now remembers whether the toolbar should be displayed or not. Changes in SecureFX 2.2 (Beta 2) -- October 2, 2003 --------------------------------------------------- New features: - When changing directories to a UNC path, the tree can now be viewed. - For SSH2 connections, the Server Principal Name (SPN) can be specified in the GSSAPI Properties dialog. Changes: - The Directory Permissions specified on the Advanced page of the Global Options are now applied when a new folder is created. - For new installations of SecureFX, the Quick Connect and Connect buttons have switched positions on the toolbar in order to be consistent with SecureCRT. - For SSH2 connections, both "GSSAPI" and "GSSAPI-MIC" are supported as explicit options for doing GSSAPI authentication. GSSAPI-MIC is the recommended option if the remote system supports it. Changes in SecureFX 2.2 (Beta 1) -- September 18, 2003 ------------------------------------------------------ New features: - Support for Kerberos v5 authentication via GSSAPI for SSH2 connections. - Support for GSSAPI secured key exchange for SSH2 connections. Mechanisms supported depend on GSSAPI provider. Only the Kerberos v5 mechanism has been tested. - The private key agent cache is now shared between SecureCRT and SecureFX, eliminating the need to reenter the passphrase for SSH2 connections. - Support for SFTP version 4. - Support for resuming multiple-file transfers. - Improved remote editing by allowing the file being edited to be uploaded to the remote server each time the file is saved on the local machine. This is a global option called "Upload when the file is saved in the editor". - Ability to delete files/directories with SFXCL. - Ability to change permissions on multiple files. - Ability to copy individual lines of text from the log window to the clipboard. - When connected to VShell for Windows version 2.2 or higher, the Properties dialog for the remote file or folder has a Security tab that allows ACL permissions to be viewed. Changes: - If a remote file is being edited by an application that locks the file, a message is reported in the log window that the file cannot be uploaded because it is locked. - The default protocol for new sessions is now SFTP instead of FTP. - Made keyboard accelerators to common menu items the same between SecureCRT and SecureFX. - Added support for parsing directory listings from VxWorks FTP servers. - Improved performance of SFTP transfers. Depending on the network topology and SFTP server, SFTP transfers are up to three times faster than with SecureFX 2.1. - Improved support for OS/400, including listings that do not include library name. - Improved error messages after a failed delete, rename, chmod, or link resolution operation. - Added /NOPROMPT flag to SFXCL. When this flag is used, it causes SFXCL to dismiss all user input prompts as though the user clicked on the Cancel button or pressed the ESC key. - Renamed "Session Configuration" and "Global Configuration" to "Session Options" and "Global Options", respectively. - Added a "Quick Connect" button to the Connect dialog's toolbar. Bug fixes: - SecureFX prompted to overwrite on upload when the file did not exist on the remote site. - When deleting a directory using SFXCL, if the directory was specified with a trailing /, the contents of the directory were deleted, but the directory was not. - SecureFX crashed on server-to-server transfers when one connection was SFTP and the other was FTP over SSH2. - SecureFX could crash if an FTP over SSH2 or SFTP session was disconnected by the user before it had connected. - SecureFX crashed when a server-to-server transfer was interrupted. - The FTP transfer mode was sometimes incorrect because it was not properly initialized by the FTP server or because SecureFX did not initialize it when resuming a transfer. SecureFX now explicitly sets the transfer mode in these cases. - SecureFX tried to reconnect after a failed FTP over SSH2 logon was canceled by the user. - Interrupted downloads failed to resume after reconnecting if the "Action for existing files" global option was set to anything other than "Confirm overwrite". - For new SFTP sessions, the username default was "anonymous". The username is now blank by default. - When connecting to a VShell server version 2.1.3 or earlier, SecureFX attempted to use SFTP version 4, which was not supported and caused VShell to disconnect. Vulnerabilities: - When using Kerberos host and user authentication via GSSAPI, the connection could be vulnerable to a man-in-the-middle attack. GSSAPI with MIC has been introduced to eliminate this risk and the GSSAPI method has been removed. Although the trace output shows gssapi as the requested authentication, GSSAPI with MIC is actually what is requested.