SecureFX(R) 3.1.4 (Official) -- September 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.1.4 (Official) -- September 14, 2006 ---------------------------------------------------------- Changes: - SFTP: Changed the default compression to "None". This only affects new installations. Bug fixes: - SecureFX crashed if the session was disconnected while a file was being uploaded. - SecureFX reported an error when attempting to connect to a host that would not resolve and closing the session window before the connection attempt timed out. Changes in SecureFX 3.1.3 (Official) -- July 25, 2006 ----------------------------------------------------- Bug fixes: - Reduced the time it takes for the Connect dialog to display, which was noticeable on a network or USB drive. - SecureFX 3.1 reported an unknown application error (E000001B) and crashed when a connection closed abnormally. - Under certain circumstances, SecureFX crashed after the "Confirm File Replace" dialog appeared. - Quick Synchronize failed when uploading a file or directory that did not exist in the target directory on the remote host. - SFTP: For SFTP 6, in the vendor-id information that was sent to the remote machine, the product version was for a library rather than for SecureFX. Changes in SecureFX 3.1.2 (Official) -- May 25, 2006 ---------------------------------------------------- Changes: - SFTP: SecureFX no longer reports a confusing trace output message about an unexpected packet size because it was not an error. Changes in SecureFX 3.1.1 (Official) -- April 25, 2006 ------------------------------------------------------ Changes: - Added support for migrating AbsoluteFTP settings to SecureFX. Bug fixes: - SFTP: SecureFX crashed when attempting to connect to VShell if "Sftp Use Single Virtual Root" was true and the user's home directory was "/". - SSH2: It was not possible to change the passphrase of a public key through the Public Key Properties dialog. Changes in SecureFX 3.1 (Official) -- March 28, 2006 ---------------------------------------------------- Bug fixes: - SFTP: SecureFX could crash when doing ASCII server to server transfers with certain files. - SFTP: When some large files or files without an EOLN at the end were uploaded as ASCII, sometimes they were corrupted. Changes in SecureFX 3.1 (Beta 4) -- March 14, 2006 -------------------------------------------------- Changes: - When a file transfer is interrupted and SecureFX prompts to resume the transfer, the full path to the file is displayed. Bug fixes: - If a generic proxy was misconfigured, it caused SecureFX to hang, and disconnecting the session caused SecureFX to crash. - The SecureFX installer added a shortcut to the SecureFX program group that linked a Help file that did not exist. - The file count progress information was incorrect for resumed transfers. - When editing the default session, it was possible do a password change. - SFTP: Under certain conditions, SecureFX could crash when doing an ASCII transfer. - SSH2: Under certain circumstances, even though an X.509 host key had been accepted and saved, SecureFX asked about accepting it during key re-exchange or when reconnecting. Changes in SecureFX 3.1 (Beta 3) -- March 2, 2006 ------------------------------------------------- Changes: - The installation program no longer removes old versions of SecureFX from Windows Add/Remove Programs. - For DNS addresses, SecureCRT uses the return list as is, rather than preferring IPv4 addresses. Bug fixes: - The local directory was continuously repainted when downloading to that directory. - In the Quick Connect dialog, changes made to the default session were only reflected for the default protocol. - SFTP: SecureFX crashed when transferring a file that no longer existed. Changes in SecureFX 3.1 (Beta 2) -- February 21, 2006 ----------------------------------------------------- New features: - SSH2: Passwords for SSH2 sessions can be changed from the Session Options dialog using the SSH2 protocol when it is supported by the remote machine. Changes: - When "FIPS mode" is enabled, invalid cryptographic algorithms are not displayed in the Session Options dialog. - When "FIPS Mode" is enabled, FTP one-time password support is disabled. - When "FIPS Mode" is enabled, it is displayed in the About box. - SSH2: Added default support for X.509 certificate server host keys. - SSH2: When a key exchange method is not supported, a message is logged to the trace output. - SSH2: Authentication methods can be edited in the Session Options dialog for SSH2 sessions that are connected. Bug fixes: - SecureFX crashed when copying a file on the remote machine to a new location on the same remote machine. - If a file was uploaded to a file that already existed on the remote machine and the new file was smaller than the existing file, the uploaded file contained the tail end of the old file. - SecureFX crashed when remotely editing an ASCII file on a UNIX or Linux server. - When SecureFX and SecureCRT were integrated and the terminal protocol for a session was set to SSH2 and the transfer protocol was set to FTP, if the password was saved, it had to be re-entered when switching between SecureFX and SecureCRT. - SSH2: Pressing OK in the GSSAPI Properties dialog caused SecureFX to crash - SSH2: When compression was on, key exchange failed during connection because SecureFX did not send the correct list of compressions. - SSH2: When "FIPS Mode" was enabled, the New Host Key dialog did not display the server's fingerprint. It is now displayed as a SHA-1 hash when "FIPS Mode" is enabled. - SFXCL: The /List command in SFXCL crashed after the command was executed. Changes in SecureFX 3.1 (Beta 1) -- January 31, 2006 ---------------------------------------------------- New features: - Enhanced support for X.509 certificate authentication. - Previously, X.509 was supported through a CAPI store. Now, X.509 certificates are also supported directly. - SecureFX supports forwarding X.509 certificates through the public-key agent. This means that authentication happens automatically when connecting to another machine using the same X.509 certificate. - SecureFX now has an administrator option to run in "FIPS Mode". When this option is set, SecureFX uses a FIPS 140-2 validated cryptographic library and only allows FIPS-approved algorithms. - The Activator supports SSH agent functionality, which means that if SecureFX is closed, authentication happens automatically as long as the Activator is still running. - Folders and multiple selected sessions can be connected from the Connect dialog. - SFXCL: SFXCL now supports /List, which lists the specified directory on the remote system. Changes: - Hidden files and folders are not displayed in the Connect dialog. - The version information in the About box can now be selected and copied. - SSH2: Modified the SSH2 page in the Session Options dialog to allow key-exchange methods to be configured. Bug fixes: - There was an apparent slowdown when browsing SMB/NetBIOS mounted shares in the Local window. - If a USB drive was inserted after SecureFX started, it was not displayed in the Local window. - SSH2: On the SSH2 page in the Session Options dialog, if no key exchange method was selected, the dialog informing that at least one key exchange method must be selected was displayed twice. - SSH2: Some Kerberos key exchange methods were listed twice in the key-exchange methods list. - SFXCL: SFXCL crashed if a session that did not have a transfer protocol was specified on the command line. - SFXCL: If a relative path was specified for the remote and the path did not exist, SFXCL attempted to change directory to an empty path.