SecureFX(R) 4.5.4 (Official) -- January 24, 2008 Copyright (C) 1995-2008 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 4.5.4 (Official) -- January 24, 2008 -------------------------------------------------------- Changes: - The license wizard now allows data for multi-year licenses to be entered manually. Changes in SecureFX 4.5.3 (Official) -- November 1, 2007 -------------------------------------------------------- Bug fixes: - File transfers could have failed if key re-exchange occurred during a transfer. - FTP/SSL: Connecting to a server that was using a certificate with a large key size, could have resulted in the following error: "The buffers supplied to a function was too small". Changes in SecureFX 4.5.2 (Official) -- August 15, 2007 ------------------------------------------------------- Changes: - Added support for CTRL+END in the log view, which puts focus at the end of the scrolling output. Bug fixes: - When SecureFX and SecureCRT were integrated, changing the file transfer protocol from None to something else could cause SecureFX to crash. - On FTP servers configured to do MSDOS-style file listings, files uploaded at midnight had a timestamp of noon. - Under certain circumstances, when a remote file was overwritten, the timestamp was incorrect. - Under Vista, the Connect dialog did not allow multiple sessions to be selected using CTRL+click. - In FIPS mode, creating OpenSSH format keys and converting private keys to OpenSSH format failed. Changes in SecureFX 4.5.1 (Official) -- May 17, 2007 ---------------------------------------------------- Bug fixes: - If the connection was lost during an upload and the session automatically reconnected and resumed the upload, the file was uploaded to the wrong folder. - The Activator no longer worked when launched directly (e.g., from a desktop shortcut). - SSH2: SecureFX crashed when attempting to convert an SSH1 key pair to OpenSSH format. Only SSH2 key pairs can be converted. - SSH2: When converting an SSH key to OpenSSH format, if the filename for the converted key was not changed and "No" was selected at the overwrite prompt, it was not possible to enter a new name. Changes in SecureFX 4.5 (Official) -- April 5, 2007 --------------------------------------------------- Changes: - SSH2: The SSH_IGNORE message is only shown in trace output when the session's trace level is set to a value greater than one. Changes in SecureFX 4.5 (Beta 4) -- March 27, 2007 -------------------------------------------------- Bug fixes: - SFTP: SecureFX crashed when the network connection was lost during a file transfer. - SSH2: SecureFX crashed when attempting to convert a file that was not a private key to OpenSSH format. Changes in SecureFX 4.5 (Beta 3) -- March 15, 2007 -------------------------------------------------- New features: - SSH2: Added support for exporting public keys from X.509 certificates. Changes: - SSH2: In order to be compliant with the IETF draft draft-saarenmaa-ssh-x509-00.txt, the SHA1 hash algorithm is used by default with X.509 RSA host keys and public keys. - SSH2: Additional certificate information is shown in the trace output and the certificate error dialog when attempting to use an X.509 certificate for authentication. Changes in SecureFX 4.5 (Beta 2) -- February 27, 2007 ----------------------------------------------------- Changes: - SSH2: For Pragma Fortress Secure Shell servers, stat attributes are ignored so that the folder name is not added to the file name during transfers. Bug fixes: - If more than one remote site was connected and a file was dragged from the local window to the queue, if the focus in a remote site was set to a file, the prompt to select the destination incorrectly included the file in the destination location. - The "*" wildcard did not correctly match files that contained multiple extensions. - After choosing to integrate SecureCRT and SecureFX, if privileges were not sufficient to write to the registry, it was possible to repeatedly be prompted to integrate. - SSH2: Attempting to change an SSH2 password from the Session Options dialog caused SecureFX to crash. - SSH2: Attempting to generate a DSA key that was not a multiple of 64 resulted in an Unknown Application Error. - FTP/SSL (explicit): Attempting to connect to an FTP SSL server that did not specify a certificate resulted in an Unknown Application Error. Changes in SecureFX 4.5 (Beta 1) -- February 8, 2007 ---------------------------------------------------- New features: - Windows Vista support. - A set of sessions can be launched automatically on startup by specifying folders or multiple sessions as auto sessions. - Added a toolbar button for launching SecureCRT if SecureFX is integrated with SecureCRT. If the active session specifies a terminal protocol, that session will be started in SecureCRT. - Files can be dragged to the transfer queue. - The transfer queue window can be resized. - Columns in the transfer queue can be hidden and shown and these settings, in addition to the column widths, are saved. - SSH2: Added support for generating OpenSSH format keys and for converting VanDyke format private keys to OpenSSH format. - SSH2: Added support for zlib@openssh.com compression. With this compression method, compression does not start until after authentication, which prevents unencrypted passwords from being cached by the zlib library. - SFXCL: Added /AcceptHostKeys option. Changes: - Removed the transfer queue window menu item "Cancel Transfer" and added the menu items "Cancel Selected" and "Cancel All". - When a remote file is saved to disk, the "Save As" dialog uses the transfer type associated with the file for the "Save as type". Bug fixes: - Server to server ASCII transfers converted newlines incorrectly for files that had Windows style newlines. - If the "Save session" option was not set when using Quick Connect, the hostname was not displayed in the title bar. - In some cases, unnecessary CWD commands were issued. - SFXCL: The /P option was not honored when /QuickSync was used.