SecureFX(R) 3.0.5 (Official) -- February 14, 2006 Copyright (C) 1995-2006 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 3.0.5 (Official) -- February 14, 2006 --------------------------------------------------------- Changes: - SSH2: For GSSAPI authentication, the default SPN was changed from host@$(FQDN) to host@$(HOST) because DNS is not a secure system. Bug fixes: - Under certain circumstances, when a session was disconnected, SecureFX reported that the connection terminated abnormally. - A buffer overflow was theoretically possible when a Unicode string was converted to a narrow string. - Local folder and file icons were not displayed when there was no C: drive. - SSH2: If GSS was supported by the server but not by the local machine and SecureFX tried to use a GSS key exchange method, it crashed. - SSH2: Using a PKCS#12 file for more than one session at a time could result in threading or synchronization problems. Changes in SecureFX 3.0.4 (Official) -- November 10, 2005 --------------------------------------------------------- Changes: - Added the summary transfer information that had been implemented in SecureFX 2.2.9. - SFTP: When generating a public/private key, if the folder selected to write the key to does not exist, the Key Generation wizard now asks if it should be created. Bug fixes: - If a file was closed within an application such as Word, TextPad, or UltraEdit and then the file was reopened through SecureFX, the application was brought to the foreground, but the file was not opened. - If the Help button was pressed in the Connect dialog, help was not displayed. - SecureFX crashed when a file with a timestamp year larger than 2038 was uploaded. - Under certain circumstances, SecureFX said that it could not integrate with CRT, even though CRT was not installed. - SFXCL: SFXCL returned success when the configuration folder could not be found. Changes in SecureFX 3.0.3 (Official) -- September 8, 2005 --------------------------------------------------------- Bug fixes: - Under certain circumstances, migrate failed with a C++ runtime error when upgrading a SecureFX session database that had host keys. - Cancelling a drag and drop to the Windows desktop left a partial file, which could not be copied over. The original behavior where an error is displayed was restored. - If the "Save session" option was set in the Quick Connect dialog, the new session was not added to the recently used session list. - Under certain circumstances, it was not possible to open the Connect dialog from the Activator menu. - SFXCL: When running in quiet mode, some output was being displayed on the screen. Changes in SecureFX 3.0.2 (Official) -- August 11, 2005 ------------------------------------------------------- Bug fixes: - In version 3.0.1, if the global option "Use outgoing data connections (PASV)" was not set, FTP downloads failed. Changes in SecureFX 3.0.1 (Official) -- July 14, 2005 ----------------------------------------------------- Bug fixes: - Canceling a drag and drop to the Windows desktop resulted in an error. - If SecureFX received a "150" reply from the FTP server after the data socket has received its data and been closed, nothing was displayed in the file pane. - SSH2: In the Public Key Properties dialog, an identity file could not be selected using the browse button. Changes in SecureFX 3.0 (Official) -- June 16, 2005 --------------------------------------------------- Bug fixes: - If SecureFX was not integrated with SecureCRT, attempting to create a session using the New Session Wizard caused SecureFX to crash. - SSH2: In the Public Key Properties dialog, if the browse button was used to select an identity file for a session, the identity file field did not get updated. Changes in SecureFX 3.0 (Beta 7) -- June 9, 2005 ------------------------------------------------ Changes: - New sessions created with the wizard use the hostname as the default session name. Changes in SecureFX 3.0 (Beta 6) -- June 2, 2005 ------------------------------------------------ Changes: - Improved handling of mismatched DLLs when SecureFX and SecureCRT are integrated. Bug fixes: - When the initial remote directory was set via the right-click menu, the change was not reflected in the Session Options dialog. - Sometimes the icons displayed in the File Types page in the Global Options dialog were incorrect and in some rare cases, SecureFX crashed. - When global logging was enabled, a subsequent instance of SecureFX could not be started. - License errors were reported as "317 and 317". - When SecureCRT and SecureFX were integrated and a session was saved using the Quick Connect dialog, a protocol did not get set for the other application. - It was not possible to integrate SecureCRT 5.0 and SecureFX 3.0 on machines if they had never been installed. - SFTP: Could not use the GSSAPI key exchange method when connecting to an IP address and other key exchange methods were also allowed. - SFTP: Attempting to use an invalid public key caused SecureFX to crash. - SSH2: The View Host Key dialog did not scroll when the host key did not fit. - SFXCL went into an infinite loop when attempting to transfer files to a non-existent SFTP root. Changes in SecureFX 3.0 (Beta 5) -- May 12, 2005 ------------------------------------------------ New features: - For new installations, the installer can optionally install sessions for over 100 FTP sites. Changes: - When SecureFX is integrated with SecureCRT, menu item "Show Terminal Sessions" on the right-click menu in the Connect dialog allows the terminal sessions to be displayed or hidden. - When SecureFX is integrated with SecureCRT, the toolbar, menu bar, and status bar settings are now separate. - The Activator now separates recent terminal and transfer sessions. - SFTP: Added support for GSSAPI group exchange as documented in draft-ietf-secsh-gsskeyex-08.txt. Bug fixes: - On MVS servers, large partitioned data sets (PDS) were not displayed correctly. - The New Session wizard was not using the Default session's protocol. - The global anonymous password setting was not being used for new sessions. - FTP: SecureFX crashed if the session window was closed when trying to connect to a host that could not be resolved. Changes in SecureFX 3.0 (Beta 4) -- April 20, 2005 -------------------------------------------------- Bug fixes: - If the WinSock 2 DLL was not currently initialized, the migration wizard crashed. - When the log view was horizontally scrolled and text was selected, the correct text did not get selected. - The global anonymous password setting was not used when a new session that used anonymous logon was created. - SFXCL crashed when attempting to use a protocol whose DLL was not installed. Changes in SecureFX 3.0 (Beta 3) -- April 5, 2005 ------------------------------------------------- New features: - Support for IPv6. Changes: - For encrypted data such as passwords and logon scripts, the encryption algorithm was changed from CAPI back to Blowfish or encoded. - Reduced the frequency of updating the transfer progress window in order to reduce the flashing and CPU usage for large transfers. Bug fixes: - Under Windows 98, SecureFX performed an illegal instruction on startup, which caused SecureFX to crash. - If the "Do not show hidden or system files" global option was set, navigating to a folder that contained hidden or system files caused a crash. - The connection retry global options were not being honored. - Under Windows XP, password characters were sometimes displayed as vertical bars instead of dots. - SecureFX crashed after canceling out of the Public Key Properties dialog under certain circumstances. - SFTP: SecureFX could hang when using GSSAPI authentication. Changes in SecureFX 3.0 (Beta 2) -- March 15, 2005 -------------------------------------------------- Changes: - Modified SecureFX to use the Windows common controls, which gives the user interface a more modern appearance. Bug fixes: - When "Save session" was checked in the Quick Connect dialog, the session was saved, but the username and password were not. - The migration wizard claimed it could not find any connection protocols in the SecureCRT 5.0 installation folder, even when they were there. - The migration wizard checked for a non-existent destination folder rather than an empty folder. - SecureFX failed to run when the migrate utility was not present. Changes in SecureFX 3.0 (Beta 1) -- March 1, 2005 ------------------------------------------------- New features: - Files can be copied between SecureFX and the Windows Explorer, the desktop, and other applications using drag-and-drop and copy-and- paste operations. - All settings can be shared between SecureFX 3.0 and SecureCRT 5.0. When SecureCRT is also installed, it is possible to launch SecureCRT and connect to specific sessions from SecureFX. The global and session options dialogs allow SecureCRT settings to be modified from within SecureFX when SecureCRT is installed. - Specify sound notifications for connect, transfer, and other events. - Added the ability to create multiple global firewalls, which can be used on a per-session basis. - Added support for a generic proxy. - SecureFX sessions can be minimized to the Activator instead of the taskbar. The Activator is a tray application that manages SecureFX sessions (and SecureCRT sessions when SecureCRT is installed). - SecureFX now has a default session. - Added support for "Use auto session". - Added support for Internationalized Domain Names (IDNs). - Initial support for IPv6 has been added. Changes: - FTP over SSH2 is no longer supported. - For encrypted data such as passwords, the encryption algorithm was changed from Blowfish to CAPI, which uses Microsoft cryptographic service providers to encrypt and decrypt data. - The FTP Account field is now stored encrypted. - For new installations of SecureFX, the default cipher for SSH2 sessions is SHA1 instead of MD5. - SecureFX's configuration is now stored in .INI files and uses the same format as SecureCRT. This change allows SecureFX to be installed on a removable drive. - Multiple instances of SecureFX can now be run. - The custom toolbar configuration is now stored in Global.ini instead of in the registry. - Moved the "Import Session Data" menu item to the Tools menu. This imports CuteFTP and WS_FTP data into SecureFX. - In the Connect dialog, moved the "Show descriptions" option from the dialog to the context menu. - During installation, the protocol(s) to be installed can be specified. - Modified the New Session Wizard to allow terminal settings to be specified when SecureCRT is also installed. - Added the filename to the file download failure error message. - When SecureFX connects to a server using FTP, the operating system is always logged. - Added beta forum link to the Help menu. - FTP: Anonymous logon is no longer the default. - SSH2: Added support for diffie-hellman-group14-sha1 key exchange. The default order is as follows: diffie-hellman-group-exchange-sha1 diffie-hellman-group14-sha1 diffie-hellman-group1-sha1 - SSH2: Modified authentication user interface so that more than two authentication methods can be specified. Bug fixes: - SecureFX crashed when a file transfer to the local desktop was resumed. - SecureFX was not handling a 550 error from PWD as a return code, which resulted in failed transfers. - Server to server transfer of a file failed when a directory was specified as the target. - SecureFX crashed if PWD returned an error during a transfer, delete, or rename. - Remote files sizes were incorrect for files over 4 gigabytes. - When the tree view was turned off and turned back on, the hard drives were no longer displayed. - Under some circumstances, it was possible for remote edit to clobber already-opened files. - When editing a file remotely, sometimes SecureFX prompted to save the file even if no changes were made and sometimes multiple prompts were issued. - It was not possible to navigate to a subfolder without having permissions to the parent folder. - It was possible to get an access violation when text was selected in the log window if the selection extended beyond the last line. - In the Quick Synchronize window, the items did not sort correctly when the Description column header was clicked. - When downloading a file that was larger than the available free disk space, SecureFX did not report that the local file system was full. - The "Save usernames" checkbox was shown when the session was a Quick Connect that wasn't saved. - SFTP: In the Quick Connect dialog, if the hostname was blank and the "Upload" button was pressed, the upload failed. SecureFX now prompts for the hostname. - SFTP: SecureFX was not setting the text transfer flag for SFTP version 4. - SFXCL failed to transfer files when the transfer was executed through the AT command. - When SFXCL was used with the /NOPROMPT and the connection failed due to a prompt, SFXCL attempted to reconnect infinitely. - When using the /NOPROMPT flag with SFXCL and the connection failed due to a prompt, reconnection was attempted infinitely.