SecureFX Changelog

What's new in SecureFX 9.5.0 Build 3182 Beta 1

Nov 2, 2023
  • New Features:
  • For FTPS and HTTPS sessions, added TLS certificate validation options "Revocation checking enabled" and "Revocation checking only uses cache".
  • Added a compatibility mode for Azure Blob SFTP servers, which automatically disables SFTP extensions.
  • Passwords for saved credentials can be updated more easily via the Tools menu.
  • Changes:
  • Hostnames containing multiple "@" characters are now supported, which allows jump hosts (e.g., CyberArk) to be specified in the hostname.
  • For failed SCP connections, the log message was changed from "The remote execute operation has been aborted." to "The operation was aborted because the channel closed."
  • Log messages for HTTPS connections no longer show the protocol as being HTTP.
  • When standalone SecureFX is installed, the button to launch SecureCRT is not shown on the toolbar.
  • SFXCL: When logging to a file, if authentication failed, the actual cause of the authentication failure would not have been logged to the file.
  • SFXCL: When a move is executed and /tracelevel is set to 2 (or higher), the log includes the attempt to delete the file and whether or not it succeeded.
  • Windows: When opening the Session Manager, performance may have been impacted due to the protocol-specific session icons.
  • A "Use Old Session Manager Icons" global INI-only option has been added to allow the use of the old generic icons.
  • Windows: The USERNAME environment variable can be embedded within a string in the Username field (e.g., %USERNAME%.admin).
  • Bug Fixes:
  • If a malformed key file was specified as the global public key, opening the Global Options dialog resulted in a crash.
  • The "Accept and Save" button was not available when connecting to a session with multiple host keys for the same host, which resulted in the prompt to accept the host key being displayed every time the session connected.
  • When an open session was disconnected and reconnected, the directory listing for the current directory was not refreshed.
  • When a cross-platform substitution variable (e.g., VDS_CONFIG_PATH) was used as part of the path to a key to load into agent at startup, the variable was replaced with the actual path.
  • If SecureFX was opened from the command line with the /Firewall option and an instance of SecureFX was already running, the specified firewall was not used.
  • When the configuration path was specified on the command line via the "/F <config path>" option, SecureFX did not honor the option.
  • When opening a SecureCRT session from SecureFX, the "Open in a tab" option was not honored.
  • If a session was configured to authenticate with a certificate from CAPI or a smartcard and authentication failed, the dialog to select a public-key file was displayed instead of the dialog to select a certificate.
  • When creating a folder in the Session Manager, if the folder was renamed as part of the addition, a secondary folder with the original "New Folder" name was also added.
  • When debug logging level 9 was enabled and the Cisco SCP shell enable password was entered, the password was not obscured in the log output.
  • With a new configuration, both the Quick Connect dialog and the Session Manager could have be shown at startup.
  • When SecureCRT and SecureFX were installed integrated and the terminal protocol for a session was changed to "Local
  • Shell" then back to SSH2, the SSH2 session options page could have appeared twice.
  • Windows: When SecureFX was running within SecureCRT's process, the applications could have crashed after waking the computer from sleep.
  • Windows: If the evaluation period ended and a license was applied from the expired license dialog, the application did not start automatically when the license wizard was dismissed.
  • Windows: When using SFXCL to connect to an FTPS or HTTPS host, if the connection resulted in a certificate validation prompt, the save certificate option was unexpectedly allowed.
  • Windows: If the session database contained a very large number of sessions and the Session Manager filter field was used to filter the session list, a long delay may have occurred.
  • Windows: When focus was within the Session Manager session view or filter field, pressing the Tab key unexpectedly moved focus to the local window.
  • Windows: When the Session Manager and Command Manager were docked within the same window as tabs, selecting the tab that did not have focus may have caused the tabs to switch position.

New in SecureFX 9.3.0 Build 2905 (Nov 4, 2022)

  • Vulnerability addressed:
  • An external report claims that when using a brute-force attack, sensitive data, such as passwords, stored in the SecureCRT or SecureFX configuration without a configuration passphrase or with a weak configuration passphrase can be cracked in a relatively short amount of time. Direct access to the configuration data is required in order to exploit this vulnerability.

New in SecureFX 9.2.3 Build 2829 (Aug 3, 2022)

  • New Feature:
  • Windows: Added an administrative option that suppresses the prompt for a configuration passphrase the first time the application runs.
  • Changes:
  • Windows: When the Quick Connect dialog is displayed, initial focus is placed in the Protocol field when the global option "Use trackable insertion caret" is checked. Otherwise, initial focus is placed in the Hostname field.
  • Bug Fixes:
  • If a session was disconnected while an alternate screen application (e.g., screen, mc) was running, the scrollback buffer was disabled when another session re-used the disconnected tab.
  • When setting the tab caption via a script, the window title was updated even if the tab running the script did not have focus.

New in SecureFX 9.3.0 Build 2803 Beta (Jun 29, 2022)

  • New Features:
  • Added an option to check for updates automatically at startup.
  • Added the ability to duplicate a session in the Session Manager or Connect dialog.
  • Added an option that forces a prompt for the hostname when the session connects.
  • Added the ability to use the algorithms [email protected] and [email protected] as OpenSSH certificate types.
  • SSH2: Added support for using the x509v3-rsa2048-sha256 algorithm for authentication (RFC 6187).
  • Windows: Added support for using rsa-sha2-256 and rsa-sha2-512 public-key algorithms as raw SSH2 keys for CAPI certificates (RFC 8332).
  • Windows: Added support for using x509v3-ecdsa-sha2* algorithms from RFC 6187 for keys in the CAPI store and as raw SSH2 keys.
  • Windows: Added an administrative option that suppresses the prompt for a configuration passphrase the first time the application runs.
  • Changes:
  • For new installations, the Session Manager is on by default.
  • The number of sessions that can be opened simultaneously before a warning is displayed can now be configured.
  • SSH2: Trace output for the host key now includes the type and size.
  • SSH2: The View Host Key dialog now includes the type and size for the selected host key.
  • Bug Fixes:
  • When connecting to an Arista switch, the file listing may not have been displayed as expected.
  • Windows: When selecting a recent session from the SecureFX taskbar icon, the session did not open as expected.
  • Windows: When selecting the "Connect..." or "Quick Connect..." options from the SecureFX taskbar icon, the expected dialog was not displayed.
  • Windows: When authenticating with a certificate from the personal CAPI store, if the "Use certificate as raw SSH2 key" option was enabled, the key was not correctly added to agent and a subsequent connection could fail with an agent signature error.
  • Windows: Multiple CAPI errors could have been reported when attempting to display a certificate fingerprint if the fingerprint for any certificate could not be obtained.
  • Windows: If the signature failed to verify for the protocol or Python DLLs, the file path displayed on the warning dialog may have been cut off.
  • Mac: If a network connection was unavailable while checking for an update via "Update Now", the error displayed did not report a helpful message.
  • Mac/Linux: When an SFTP session was connected to a remote UNIX server, uploading a file that contained a colon character as part of the filename would have been uploaded to the remote user's home directory instead of the current working directory.

New in SecureFX 9.2.2 Build 2794 (Jun 29, 2022)

  • Bug Fixes:
  • If a saved credential was modified while editing multiple sessions simultaneously, SecureCRT could have crashed.
  • When a newly generated public key was saved in OpenSSH format, the key could not be used for authentication due to an incorrect file format error.
  • When editing multiple sessions at once, the port field could not be changed.
  • When using the "Personal data folder" option, if a session option was modified, the personal data store options could have been saved to the non-personal configuration.
  • Windows: When using the Microsoft Pinyin Input Method Editor toenter Chinese characters in fields that contained hint text (e.g., Session Manager filter field), the hint text was not cleared when the Chinese characters were entered.
  • Mac: If SecureFX crashed and the user chose to report the crash, the email template used for the report may not have contained the correct version of SecureFX.

New in SecureFX 9.2.0 Build 2755 (Apr 27, 2022)

  • Bug Fix:
  • On certain systems, when clicking on some web links displayed in the application, the expected page may not have been displayed in the web browser.

New in SecureFX 9.2.0 Build 2693 Beta 2 (Feb 4, 2022)

  • Changes:
  • Added the ability to used saved credentials when creating an SFTP session with the New Session Wizard.
  • Added the ability to access the Manage Saved Credentials dialog from the Tools menu.
  • The full path of the destination file is now displayed in the Export Settings output.
  • Bug Fixes:
  • If an upload was initiated to a session in which the connection had not been established, SecureFX could have crashed.
  • If the default session had a saved credential specified, creating a new credential could have resulted in a crash.
  • If the default session was configured to use a set of saved credentials, adding a new set of credentials could have resulted
  • in all other saved credentials being modified with the settings
  • from the new set of credentials.
  • Saved credentials were not stored in the correct location when the personal data folder option was toggled.
  • If the Public Key Properties dialog was opened and closed when a new set of saved credentials was being added, the credentials were prematurely saved, which resulted in a error being reported when the credentials were explicitly saved by closing the dialog.
  • Under certain scenarios, resuming an interrupted transfer that included subfolders may not have transferred all files.
  • Mac/Linux: After creating a public key from the Credentials Manager, an offer to upload the key was presented, and if the user chose to upload the key, SecureFX crashed.
  • Mac: When uploading a large directory structure with parallel transfers enabled, some files within the directory structure may not have been uploaded.
  • Mac/Linux: When selecting "Remove All" from the Transfer Queue, the column labels were also removed.

New in SecureFX 9.2.0 Build 2659 Beta 1 (Jan 4, 2022)

  • New Features:
  • Added a Credentials Manager that allows SSH2 and SFTP authentication credentials to be saved and used for multiple sessions, which makes it easier to change saved passwords or other credentials.
  • Added the ability to issue a sudo command when connecting to an SCP session.
  • SSH2: When attempting an SSH2 connection, if the Cipher or MAC algorithm negotiation fails, SecureFX offers to enable a supported algorithm and try again.
  • SSH2: Added the ability to use PPK3 files for public-key authentication.
  • SSH2: Added support for PPK keys that use the -cert-v01@openssh algorithm.
  • Changes:
  • For newly-generated RSA host keys, the minimum size is now 1024 bits.
  • Windows: In FIPS mode, digital signatures that use SHA-1 as the hashing algorithm can no longer be used because they are not allowed by the upgraded version of the FIPS library module.
  • The Properties dialog shows the size of the selected files or folder.
  • Modified the Quick Connect dialog so that the "Show quick connect at startup" option can be saved without having to connect.
  • Windows: When SecureCRT and SecureFX are integrated, if a scratchpad or script editor is active when SecureFX is launched from SecureCRT, SecureFX will not attempt a connection.
  • Bug Fixes:
  • Attempting to use an ecdsa-sk or ed25519-sk type public key resulted in a crash.
  • Under certain scenarios, file transfers and synchronize operations involving FTPS or HTTPS sessions could hang.
  • When authenticating with a 512-bit RSA key, if the rsa-sha2-512 signature algorithm was used, authentication failed.
  • When connecting to an MVS system, if a relative path was specified for the initial remote directory, SecureFX may not have been able to determine the fully-qualified path, causing the initial directory change to fail.
  • If the configuration was located on a network share, using the session filter search within the Session Manager could have caused a momentary hang.
  • Under unique circumstances, when connected to an OpenSSH server that had the MaxSessions option set to 1, directory browsing could have failed with a channel open error.
  • After a synchronize operation completed, the transaction statistics displayed in the log reported an incorrect number of file transfers and did not report the number of files that were deleted.
  • Under certain scenarios, firewall name changes were not immediately reflected in the Session Options dialog for sessions that used the firewall.
  • If a Putty-generated private-key file (.ppk format) was specified as the session public-key file, the "Upload" button was unexpectedly disabled.
  • Windows: When closing SecureFX after certain synchronize operations, a crash could occur.
  • Windows: When authenticating with an OpenSSH Trusted Certificate, if the private key was in the agent, authentication failed.
  • Windows: If the application was under heavy load, drop down and context menus could be slow to display.
  • Windows: On certain option fields that could display a horizontal scroll bar (e.g., GlobalSSH2 Fingerprint field), if the display was scaled above 100%, the scroll space was not calculated correctly.
  • Mac/Linux: If a file transfer was in progress when the network connection was interrupted, that transfer could not be manually cancelled.
  • Mac/Linux: If a session name included multiple ampersand characters ("&") in sequence, not all of the ampersand characters appeared on the session tab label.

New in SecureFX 9.1.1 Build 2638 (Dec 5, 2021)

  • New Feature:
  • Windows: SecureFX 9.1.1 is compatible with Windows 11
  • Bug Fix:
  • After a synchronize operation completed, the transaction statistics
  • displayed in the log reported an incorrect number of file transfers
  • and did not report the number of files that were deleted

New in SecureFX 9.1.0 Build 2571 Beta 5 (Aug 25, 2021)

  • Bug Fixes:
  • Listing all S3 buckets on a Linode server failed with a "SignatureDoesNotMatch" error.

New in SecureFX 9.1.0 Build 2560 Beta 4 (Aug 16, 2021)

  • Bug Fixes:
  • The listing of S3 buckets containing millions of items is significantly faster. Previously, it could have taken 30 minutes or longer
  • When connected to an S3 server, if the owner name for a directory entry contained a space, browsing the directory structure would have failed

New in SecureFX 9.1.0 Build 2544 Beta 3 (Jul 23, 2021)

  • Bug Fixes:
  • When connected to a NetApp StorageGRID S3 server, file rename operations may have failed
  • SCP: When connected to a Cisco ASA device that is configured to be in "Multiple Context Mode", the remote SCP commands sent by
  • SecureFX would have failed. A "SCP Cisco ASA Force System Command Mode" session .INI-file-only option has been added, which allows the remote system context to be changed to system execution mode
  • Windows: When editing an existing Scheduled Task, the start time for the task displayed the current time instead of the previously scheduled time
  • Windows: If an error occurred while attempting to update the application using "Update now...", the error message may not have been displayed as expected

New in SecureFX 9.1.0 Build 2525 Beta 2 (Jun 30, 2021)

  • Bug Fixes:
  • When connected to a Cisco device using the SCP protocol, commands sent and responses received may have been logged out of order.
  • When connected to a Treck FTP server, directory listings may not have been parsed correctly.

New in SecureFX 9.1.0 Build 2507 Beta (Jun 3, 2021)

  • New Feature:
  • Mac: Added support for Big Sur.
  • Added transfer protocol "HTTPS (S3)", which supports S3-compatible services in addition to AWS.
  • Added OpenSSH Agent support for the rsa-sha2-256 and rsa-sha2-512 signature formats.
  • Windows: The display theme's foreground and background colors are honored for the panes in the SecureFX application window.
  • Mac: Updated the GUI by removing the toolbar and moving the toolbar items to the title bar.
  • Changes:
  • The log trace level can now be set in the Session Options dialog.
  • The folder tree area in the remote view now has a minimum height.
  • Windows: For all display themes, the title bar now uses the standard Windows Minimize, Restore, and Close buttons and uses the system accent color if the Windows Colors option "Title bars and window borders" is set.
  • Bug Fixes:
  • Windows: If the local or remote window tree view was toggled on and the previously saved size of the view was set to 0, SecureFX could have crashed.
  • Windows: On high-DPI monitors with certain scaling levels, the MD5 fingerprint displayed on the view host key dialog may have been cut off.

New in SecureFX 9.0.1 Build 2451 (Mar 18, 2021)

  • Change:
  • Restored the ability to use the SHA1-96 and MD5-96 MACs.
  • Bug fix:
  • If the remote server was shut down during a synchronize operation, SecureFX did not automatically attempt to reconnect to the server.

New in SecureFX 9.0.0 Build 2422 Beta 6 (Feb 10, 2021)

  • Changes:
  • Windows: When using a PKCS#11 provider DLL that did not match the architecture (32 vs. 64 bit) of the client, a misleading error was displayed. The error message has been modified to describe the error more accurately
  • Bug fixes:
  • Windows: When renaming a file in the local window that would have resulted in a naming conflict with an existing file, under certain circumstances, SecureFX could crash
  • Windows: When viewing the Session Options dialog, certain display configurations resulted in scroll bars appearing in the category tree

New in SecureFX 9.0.0 Build 2411 Beta 5 (Jan 28, 2021)

  • Changes:
  • Windows: When using a PKCS#11 provider DLL that did not match the architecture (32 vs. 64 bit) of the client, a misleading error was displayed. The error message has been modified to describe the error more accurately.
  • Bug fixes:
  • Windows: When renaming a file in the local window that would have resulted in a naming conflict with an existing file, under certain circumstances, SecureFX could crash.
  • Windows: When viewing the Session Options dialog, certain display configurations resulted in scroll bars appearing in the category tree.

New in SecureFX 9.0.0 Build 2359 Beta (Nov 22, 2020)

  • New Feature:
  • Linux: Added support for Ubuntu 20.04.
  • Changes:
  • The prompt for keys that are pre-loaded into agent now shows the filename associated with the key.
  • SSH2: When attempting an SSH2 connection, if KEX algorithm negotiation fails, SecureFX offers to try again by enabling a supported algorithm.
  • The SHA-2 base64 hash of the public-key fingerprint is now displayed in the Public Key Properties and trace output.
  • Bug Fixes:
  • When connected to an Amazon S3 session, "pseudo" folders did not appear in the file listing. A new session INI-file-only option ("AWS Allow Pseudo Directories") has been added to allow pseudo folders to appear in the file list.
  • When the initial local window directory was a network share, there may have been a long delay at startup.
  • Windows: When connected to an Amazon S3 instance, certain object types may not have been displayed in the file view.
  • Windows: When SecureCRT and SecureFX were installed as a combined installation (integrated) and the TFTP server had been disabled via the Administrative Template, the TFTP options page was still displayed in the SecureFX Global Options dialog.
  • Mac: When SecureFX and SecureCRT were both installed, opening the terminal font dialog for a session from within SecureFX caused a hang.
  • Mac: Attempting to authenticate using a YubiKey smart card with the "opensc-pkcs11.so" library specified as the PKCS#11 provider resulted in an error, because the library could not be loaded.
  • Mac: When connecting to a FTPS or HTTPS server in which the SSL certificate was expected to validate on the local system, the connection only succeeded if the "Disable certificate validation" option was disabled.
  • Mac: When Dark Mode was enabled and the system highlight color was set to graphite, hovering over the list view in the local or remote window resulted in a white highlight color.
  • Mac: When using the built-in trackpad on a MacBook to drag a session to a different location in the Session Manager, auto- scroll and folder auto-expand did not work consistently.
  • Mac: When attempting to open a remote file using Visual Studio Code, if VS Code was already running on the system, the remote file was not opened.
  • Mac: If the Session Manager was docked and in auto-hide mode, a "<>" text artifact appeared on the Session Manager tab when expanded.
  • Mac/Linux: If the remote directory specified for a synchronize operation already existed, certain servers returned a "File not found" error instead of a "File exists" error when SecureFX attempted to create the remote directory. This caused SecureFX to terminate the synchronize operation. SecureFX now checks to see if the remote directory already exists and continues with the
  • synchronize operation.
  • Mac/Linux: When a public key that had a comment specified in the key data was added to the agent, the Manage Agent Keys dialog did not display the comment.
  • Mac/Linux: Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected and/or copied.
  • Mac/Linux: When attempting to create a QuickSync or Synchronize session to a PureFTPd server, if the remote path specified was "/", the configuration failed due to a directory creation error.
  • Linux: When using SFXCL for an HTTP operation, the process could hang or crash on exit.
  • Linux: When connected to an Amazon S3 session, buckets in certain regions may not have been accessible.

New in SecureFX 9.0.0 Build 2336 Beta (Oct 21, 2020)

  • Bug Fixes:
  • When exporting the configuration to a file, if a folder name was specified instead of a filename, the export file was created using the folder name and the folder itself was renamed with a ".bak" extension.
  • When SecureCRT and SecureFX were installed as a combined installation (integrated) and the SecureFX Session Manager option "Show Terminal Sessions" was off, SecureCRT local shell sessions were still shown.
  • Windows: If some parent path component of the local window directory was not accessible to the user, the local window could not be interacted with and the main window could not be closed.

New in SecureFX 8.7.3 Build 2279 (Aug 11, 2020)

  • Bug fixes:
  • When the latest version of SecureFX was installed, running "Check for Updates" or "Update Now" incorrectly reported that an update was available.
  • Windows: On high DPI monitors with a large scaling factor set, text displayed on the Keyboard Interactive authentication prompt could have been cut off.
  • Windows: When using CAPI to access a certificate located on a smart card and the CAPI store contained multiple certificates, there could be a delay before being prompted for the smart card pin.
  • HTTPS: When connecting to an HTTPS (WebDAV) server, if a failed authentication attempt was immediately followed by a successful attempt, the connection still failed.
  • Mac/Linux: Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected or copied.

New in SecureFX 8.7.2 Build 2214 (May 14, 2020)

  • Bug fixes:
  • Windows: When synchronized file browsing was enabled, changing folders in rapid succession in the local window could have resulted in a crash.
  • Mac: Attempting to authenticate using a YubiKey smartcard with the "opensc-pkcs11.so" library specified as the PKCS#11 provider resulted in an error, because the library could not be loaded.
  • Mac/Linux: If the remote directory specified for a synchronize operation already existed, certain servers returned a "File not found" error instead of a "File exists" error when SecureFX attempted to create the remote directory. This caused SecureFX to terminate the synchronize operation. SecureFX now checks to see if the remote directory already exists and continues with the synchronize operation.

New in SecureFX 8.7.1 Build 2171 (Mar 17, 2020)

  • Changes:
  • SSH2: When doing public-key authentication, if there is no corresponding private-key file without an extension and there is a private-key file with a .ppk extension, it will be used.
  • Bug fixes:
  • When transferring multiple files at once to or from a Microsoft IIS FTP server, some of the transfers may not have completed.
  • In the Manage Agent Keys dialog, the columns expanded every time the dialog opened, which eventually caused all column headers to disappear.
  • Mac/Linux: In the Session Manager, when attempting to give a folder a name that conflicted with an existing folder name, the original or default name was used, instead of allowing a different name to be specified.

New in SecureFX 8.7.0 Build 2143 (Feb 11, 2020)

  • Changes:
  • SFTP: Keyboard-interactive authentication works with a prompt that contains "password" with any combination of upper and lower case letters (e.g., "Password" or "PASSWORD").
  • SFXCL: Keyboard-interactive authentication works with a prompt that contains "password" with any combination of upper and lower case letters (e.g., "Password" or "PASSWORD").

New in SecureFX 8.7.0 Build 2109 Beta 3 (Jan 11, 2020)

  • Changes:
  • When a remote session that will pair with a local window is connected, a new local window is opened and paired with the remote window. If only a local window is open when the remote session is connected, it will pair with that local window
  • Added a global option that suppresses dependent session updating when a session is moved or renamed
  • Windows: The tabs of paired local and remote windows now have the same color background. For some display themes, there's a colored line over the tab
  • Bug fixes:
  • SFXCL: When an SFXCL synchronize operation completed and was exiting, the application could crash
  • SFXCL: When SFXCL reported a prior crash, the crash report was displayed in a pop up dialog. If SFXCL was running as an unattended process, this caused the process to hang waiting for the dialog to be dismissed. SFXCL now displays crash reports in the console window

New in SecureFX 8.7.0 Build 2079 Beta (Nov 21, 2019)

  • New features:
  • Added support for the HTTPS (WebDAV) file transfer protocol.
  • Added support for remote server file copies. This feature allows a remote file to be copied to another location on the same server without a download-upload sequence. This feature works with SFTP servers that have implemented the "copy-file" SFTP extension, HTTP WebDav servers, and some SCP servers.
  • Added the ability to open multiple local windows within SecureFX. A session that is doing synchronized browsing has its own local window.
  • The Session Manager and Connect dialog session filter fields now have the ability to filter sessions based on the top level folder the sessions reside in. When filtering, the folder name must be followed by the forward slash character in order to list the sessions within that folder.
  • SSH2: Added support for the diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, and diffie-hellman-group18-sha512 key-exchange algorithms.
  • SSH2: Added support for x509v3-ecdsa-sha2 algorithms per RFC 6187 for PKCS #11.
  • Added support for the FTP MFF, MFMT, and SITE UTIME commands. These commands allow the timestamp to be set on a remote file that has been uploaded to the FTP server.
  • Added support for the FTP MFF Unix.Mode command. This command allows folder and/or file permissions to be set on the remote FTP server.
  • Added a "Use Copy to Preserve Permissions" global INI-file-only option that allows remote file copy operations to preserve the target file's permissions when being overwritten. This feature works with servers that support remote file copies.
  • Added the ability to use URLs in synchronize operations in both SecureFX and the SFXCL command-line utility.
  • SFXCL: Wildcards can be used with the /CHMOD command-line option.
  • Mac: Added support for Dark Mode on macOS 10.14 and later.
  • Mac: Added a session option "Move deleted local files to the Trash" that specifies whether or not local files deleted during transfer and synchronize operations should automatically be put in the system Trash folder.
  • Windows: Added a new firewall type "Proxy command" which allows a local proxy command to be run when connecting to a remote server.
  • Windows: Added a global option for specifying which TLS versions are allowed.
  • Linux: Support for Ubuntu 19.04 has been added.
  • Changes:
  • Mac: macOS installers are now notarized by Apple. This tells Gatekeeper on the system that the software has been scanned by Apple for malicious software and is trusted.
  • It is now possible to save sessions that were created using Quick Connect, the Connect bar, or the command line.
  • If a firewall name is changed, any sessions using that firewall are updated with the new firewall name.
  • If a session is renamed or moved, any sessions using that session as a dependent session firewall are updated with the new session name or location.
  • When deleting a synchronize session, a confirmation dialog is displayed before the synchronize session is deleted.
  • When deleting a key from agent, a confirmation dialog is displayed before the key is deleted.
  • With smart card authentication, the presence of the private key is verified before attempting to use the corresponding public key.
  • When generating a new RSA key, the default size is now 3072 bits.
  • SSH2: If a session's username is empty and the saved password is empty or incorrect, the username is now saved when it is entered in the Enter Secure Shell Password dialog and the "Save password" option is checked. Previously, the username could be entered in the dialog, but was not saved to the session.
  • Added VxWorks to the list of FTP/SFTP operating systems in the Session Options dialog.
  • The product version is now shown in the expired license dialog.
  • SecureFX now logs when the SSH_MSG_USERAUTH_PK_OK response is received from the server during public-key authentication.
  • TLS session context information, including whether TLS session resumption was used, is now logged.
  • For FTP and SCP connections, the operating system for the remote machine or device is now logged.
  • When the logging verbosity is set to level 8 or higher, SecureFX logs the PGP commands executed.
  • Removed a "SUMMARY:" tag from several log lines that summarized the transfer results.
  • Windows: The VanDyke Update utility now reports the actual error text, rather than just an error number, when checking for updates fails.
  • Bug fixes:
  • If an SFXCL connection that was using an HTTP or Generic proxy was closed before the proxy command was sent, the application could have crashed.
  • Canceling an SFXCL synchronize operation could cause the application to crash.
  • If the SecureFX main window was closed while a synchronize comparison operation was in progress, the application could crash.
  • In certain scenarios, SecureFX could crash after initiating a transfer using drag and drop.
  • Under certain circumstances, when re-prompting for authentication credentials after a failed authentication attempt, SecureFX could crash.
  • When uploading a large number of files to certain FTP servers, the transfer could fail, and in rare circumstances, SecureFX could crash.
  • If a string greater than 5000 characters in length was entered in certain fields (Connect Bar, Search Filter, etc.), SecureCRT could freeze.
  • When the remote directory specified for a synchronize session already existed on the remote server as a file, this was not recognized as an error and the Synchronize dialog could not be dismissed.
  • If the network connection was interrupted during a synchronize operation, the state of the operation could become invalid.
  • The remote file path browse button in the Quick Synchronize and Synchronize Session Properties dialogs did not work if the remote system was a VShell for Windows FTP server.
  • When connected to a server that did not include file attributes in directory listings, the transfer window displayed downloaded files with a size of 0 and transfer progress did not update.
  • When using the personal data configuration option, it was possible to get into a situation where both the main configuration folder and the personal data folder were pointing at the same location, which could have caused the personal data (e.g., usernames, passwords, etc.) to be lost.
  • When an invalid or expired license was encountered at startup, SecureFX failed to look in other locations for a valid license.
  • When an FTPS or HTTPS connection was interrupted during a file transfer, the connection did not attempt to reconnect and resume the transfer.
  • In rare circumstances, an FTP transfer could appear to fail if a read request occurred after all of the data had been received and processed.
  • If the tree view was off and a remote session tab (or the local tab) was closed and re-opened, the tree view was half the width of the session view.
  • When configuring a dependent session as a firewall (jump host), a session that was invalid for the current session could have been selected by double clicking the invalid session.
  • When the Session Manager or Connect dialog tree was arranged manually, folders may not have been displayed in the expected order.
  • When using the Session Manager, changes made to existing sessions by a configuration import were not shown until SecureFX restarted.
  • When SecureCRT and SecureFX were installed as a combined installation (integrated) and a configuration import or export operation was performed from SecureFX, SecureCRT's button bar configuration was not included in the import/export.
  • If an invalid initial remote directory was specified for a session, the error was logged with unexpected blank lines.
  • When the logging verbosity was set to level 9 (packet trace), lines that exceeded a certain length were not displayed in the log view as expected.
  • Windows: On some Windows operating systems, starting SecureCRT could cause all desktop icons to refresh.
  • Mac/Linux: Connecting to a server that was configured with a 4096-bit DSA host key could result in an unsupported bit size error.
  • Mac/Linux: Creating a synchronize session in which the remote session was using the SCP protocol could have failed with a create directory error.
  • Mac/Linux: FTPS data connections failed to reuse the TLS session context negotiated for the control connection.
  • Mac/Linux: For certain FTP servers, when attempting to configure a synchronize session, if the specified remote path already existed, the synchronize session properties could not be saved.
  • Mac/Linux: When clicking the "View Host Key" button on the New Host Key dialog, the host key was rejected instead of being displayed.
  • Mac/Linux: Under certain circumstances, the expanded/collapsed state of the folders in the Session Manager could reset to the state they were in at application startup.
  • Mac: Under certain circumstances, if multiple parallel transfers were started and exactly one transfer failed, SecureFX could crash.
  • Mac: When the VoiceOver accessibility option was enabled on the system, SecureFX could crash when certain dialogs were opened.
  • Mac: SecureFX could crash on macOS 10.13 if a synchronization operation was cancelled while a transfer was in progress or pending.
  • Mac: On macOS 10.14, certain drag and drop operations (e.g., dragging a session within the Session Manager) could have resulted in a system accessibility dialog requesting additional access be granted to the application.
  • Mac: If the system launched SecureFX automatically (e.g., after a system reboot or user logon), a "-psn_<serial #>" parameter may have been included by the system as an option to the SecureFX process, causing SecureFX to attempt to connect to that parameter as a host. SecureFX now ignores the "-psn_" system parameter.
  • Mac: Dragging a session or folder into another folder caused that session or folder to be hidden from view. The moved session or folder was displayed correctly after SecureFX restarted.
  • Linux: On Ubuntu 19.04, when running SecureFX on certain older hardware, the application could crash at startup.

New in SecureFX 8.5.3 (Feb 13, 2019)

  • Change:
  • Treat the [email protected] key-exchange algorithm as synonymous to the curve25519-sha256 algorithm.
  • Bug fixes:
  • If an FTP session had a session firewall configured, SecureFX could crash when connecting to the session.
  • When connecting to PureFTPd using FTP, symlinks were displayed as files rather than as directories.
  • SFXCL: Authentication failed if /NoPrompt and user:pw were specified on the command line when keyboard-interactive authentication was used.
  • Mac: If text with trailing newlines was pasted into the Connect bar, the text was not visible.

New in SecureFX 8.5.2 (Nov 16, 2018)

  • New feature:
  • Added support for the curve25519-sha256 key-exchange algorithm.
  • Bug fixes:
  • If an OpenSSH format key was manually added to the host key
  • database, SecureCRT crashed when attempting to connect to a host
  • that used that key.
  • If the Session Manager was pinned and the active session had keyword
  • highlighting on and it was toggled off by selecting "Keyword
  • Highlighting" from the Options menu and then the Session Manager was
  • hidden, keyword highlighting was re-enabled.
  • Windows: In the Command Window, if the option "Send Characters
  • Immediately" was set, pressing CTRL+A selected all the text in the
  • Command Window instead of sending the CTRL+A to the session(s).
  • Windows: When using the mouse wheel to scroll session output, there
  • was a dead spot in the terminal area where scrolling stopped if the
  • mouse cursor was positioned there.
  • Windows: Attempting to display the Activator's About box caused an
  • error message to be displayed.
  • Mac/Linux: If the Session Manager was undocked and redocked, the
  • terminal area size changed.
  • Mac: SecureCRT could crash if a session had a dependent session and
  • the wrong password had been saved for both sessions and the wrong
  • password was entered when attempting to connect to the session.
  • Mac: If CTRL+<down arrow> was used to select multiple folders in the
  • Session Manager or Connect dialog and then arrow keys were pressed,
  • the selection could not be cleared.
  • Linux: On Ubuntu 18.x, when running Midnight Commander, if CTRL+O
  • was used to show and hide panels until there was no command prompt
  • and then Midnight Commander was restarted as root and CTRL+O was
  • used to hide panels, the command prompt was at the top of the window
  • and new output was displayed incorrectly.

New in SecureFX 8.5.1 (Sep 28, 2018)

  • Bug fixes:
  • Windows: On Windows Server 2008 R2, the icons in the Session Manager and Connect dialog were not drawn correctly.
  • Windows/Mac: Synchronize operations that deleted local files did not honor the option "Move deleted files to the Recycle Bin/Trash".
  • Changes:
  • The session channel window size was increased in order to use all available bandwidth for SCP downloads.

New in SecureFX 8.5 (Aug 29, 2018)

  • Bug fixes:
  • SecureFX crashed if an SCP session was closed immediately following an initial "cd" exec request.
  • SecureFX could crash if a new folder was created in the Session Manager or Connect dialog and there was at least one other folder under "Sessions" and then sorting was changed to manual arrangement and a session was dragged to be between the "Session" folder and the top folder.

New in SecureFX 8.5 Beta 5 (Aug 17, 2018)

  • Bug fixes:
  • If the global INI-file-only option "SecureFX Single Instance" was off and SecureFX was configured to log to a file, if a second instance of SecureFX was opened and the OK button was pressed on the dialog to select another log file and the file browse dialog was cancelled, SecureFX crashed.
  • SecureFX crashed when a folder that contained thousands of files was downloaded using SCP.
  • SFXCL: When /NoPrompt was specified for a session that used keyboard interactive authentication and the session contained the password or it was specified on the command line, authentication failed.

New in SecureFX 8.5 Beta 4 (Aug 10, 2018)

  • Bug fixes:
  • The file listing for a remote system could be very slow when the
  • folder contained many subfolders (over 10,000).
  • Pressing ENTER on the ".." folder no longer went up one level.
  • When the "pwd" command was issued to get the initial directory for
  • the remote system and an error was returned, SecureFX attempted to
  • use the error message as the path for the "cd" command.
  • Directories were not listed in sessions connected to a BusyBox
  • device (Dropbear SSH) using SCP.
  • When OneDrive was disabled, it was displayed as a file rather than
  • a folder.
  • The Beta expiration notice was displayed more frequently than it
  • should have been when SecureFX was not closed and other instances
  • of SecureFX were started/opened/launched.
  • Mac: When a session was configured to use GSSAPI authentication,
  • if GSSAPI authentication failed, a warning dialog to this effect
  • was still displayed when "Do not show this message again" was
  • checked.
  • Mac/Linux: The ".." folder could be deleted using the Delete
  • keyboard accelerator.
  • Mac/Linux: The keyboard shortcuts did not work in the Log pane.

New in SecureFX 8.3.4 (Jul 13, 2018)

  • Bug fixes:
  • SecureFX could crash when disconnecting an SFTP session.
  • Linux: The SecureFX installer failed on Ubuntu 17.

New in SecureFX 8.5.0 Build 1689 Beta 1 (Jun 28, 2018)

  • NEW FEATURES:
  • The Manage Bookmarks dialog allows bookmarks to be edited, copied from another session, added, and deleted.
  • When "Open Bookmarks" is selected from the File menu or file view context menu, all the bookmarks are shown. If there a lot of bookmarks, the list may have to be scrolled to see all of them.
  • Added a global INI-file-only option called "SecureFX Single Instance", which is on by default. If SecureFX is already running and a new SecureFX session is launched from SecureCRT, from the system desktop, or from the command line, the new session will open in the existing SecureFX application window.
  • Added support for the SHA2-512-EtM and SHA2-256-EtM MACs.
  • Added a global option to make the default action "Transfer" when a file is double-clicked or is selected and ENTER is pressed.
  • Sorting on columns is supported in all list controls that have columns.
  • Added a session INI-file-only option "Keyboard Interactive Prompt" that allows the expected prompt for keyboard-interactive authentication to be specified.
  • SFXCL: Added a /ReconnectCount flag to SFXCL that specifies the number of times to try to reconnect after a disconnect occurs during a transfer operation.
  • SFXCL: Added a /Parsable option to the /List command, which forces the list output to be displayed in MLSD/MLST format.
  • SFXCL: Added command-line option /MaxParallel that allows the maximum number of parallel transfers to be specified for transfer operations.
  • SFXCL: Added command-line option /TraceLevel that allows the trace output verbosity to be specified for all file operations.
  • CHANGES:
  • Improved the responsiveness of the user interface when multiple files are being transferred simultaneously.
  • The default action for pressing ENTER or double-clicking a file is transfer. This setting can be changed in the Global Options dialog.
  • In the Public Key Properties dialog, the "Use identity or certificate file" field can be left blank.
  • Because of an update to a cryptographic library used by SecureFX, newly generated DSA keys are now restricted to 1024 bits.
  • Preceding and trailing whitespace is removed from hosts entered in the Connect bar.
  • The Manage Bookmarks dialog is resizable.
  • The keyboard shortcut ALT+N brings up the Session Manager or Connect dialog.
  • Migrated trace level option for sessions to a higher number because most of the messages that were previously traced at level 1 were moved to level 2.
  • The session option "Disable initial SFTP extensions" can now be configured in the GUI.
  • Windows: Improved transfer speeds by more than 25% when thousands of files are transferred in parallel using the transfer queue.
  • Windows: For the VS2018 Dark theme, the active tab's color was lightened and the highlight outline color for selected options on the toolbar was changed to orange.
  • Windows: The close button for the "Native" display theme is now a plain "X".
  • BUG FIXES:
  • SecureFX crashed after closing a remote session tab and then entering text in the Session Manager's filter bar.
  • SecureFX could become non-responsive after uploading thousands of files listed individually using the transfer window instead of the transfer queue.
  • In the Session Manager or Connect dialog, if a folder was renamed to have a name that was too long for the local system, the sessions contained in the folder were deleted.
  • On case-sensitive file systems, synchronize operations could incorrectly match or miss entries where the file or folder names only differed by case.
  • On case-sensitive file systems, the entry selected in the tree view after a file operation could be incorrect if the operation involved folders or files with names that only differed by case from other folders or files.
  • Remote edit would not upload files when changes were made without exiting the editor.
  • Files could not be uploaded to a folder that did not already exist on a Titan server when SFTP version 6 was used.
  • SFXCL: Usernames, passwords, and configuration passphrases containing non-ANSI characters could not be entered at an interactive prompt.
  • SFXCL: If "/S:i" was specified on the command line, the remote initial directory was ignored if the destination filename was different from the source filename.
  • Windows: If a file on the remote system had a timestamp with a year beyond 9999, SecureFX could crash when the folder containing that file was viewed.

New in SecureFX 8.3.3 Build 1646 (May 3, 2018)

  • Bug fixes:
  • SecureFX crashed if an FTP session was disconnected after viewing
  • the Properties dialog for a remote file.

New in SecureFX 8.3.2 Build 1584 (Feb 8, 2018)

  • Bug fixes:
  • When using Quick Connect, if a firewall that was just created was specified, the firewall was not used when the session connected.
  • Extracting a public-key file from a private key failed with ECDSA keys that were created with ssh-keygen.
  • If an illegal character was used in the name of a synchronize session, the synchronize session was not written to disk.
  • Synchronization session names are now validated to ensure that they do not contain illegal characters.

New in SecureFX 8.3.1 Build 1537 (Feb 8, 2018)

  • Bug fixes:
  • SecureFX was not able to correctly parse a URI with two '@' characters (e.g., user@domain@host).
  • It was not possible to cancel transfers from the transfer tab using the keyboard.
  • Windows: SecureFX could not be installed on Windows Server 2008.
  • Windows: The 32-bit version of SecureFX was not able to transfer a 5 GB or larger file using SCP.
  • Windows: If the Connect bar was moved to the menu bar using the Customize dialog, auto complete in the Connect bar no longer worked.
  • Windows: Many dialogs had display issues on high-DPI monitors when the system was scaled to 125% or 175%.

New in SecureFX 8.3.0 Build 1509 Beta 4 (Nov 2, 2017)

  • Change:
  • Added icons for many menu items, which are displayed in the menus on Windows and can be used to customize the toolbar on Windows and Mac.
  • Bug fixes:
  • SecureFX could crash when a parallel transfer upload was cancelled.
  • When SecureCRT and SecureFX were integrated and the "Cache session password" option was on, if quick connect was used to connect to an SSH2 host that used password authentication and then SecureFX was launched, automatically connecting to the same SSH2 host, the password had to be re-entered.
  • Windows: SecureFX could crash when the computer woke from Sleep or Hibernate mode.

New in SecureFX 8.3.0 Build 1491 Beta 3 (Oct 12, 2017)

  • Bug fixes:
  • SFXCL returned a success code when a command failed to run because the evaluation license had expired.
  • The Move up, Move down, and Play (sound) icons in dialogs did not display correctly on high-DPI monitors.
  • Windows: SecureFX crashed in the Windows 10 Creators Update when a smart card (PIV/CAC) was used.

New in SecureFX 8.3.0 Build 1474 Beta (Sep 22, 2017)

  • New features:
  • Improved the performance of synchronization operations involving large numbers of files and folders.
  • Improved the performance of listing large local directories. SFXCL now returns the following exit codes:
  • 0 (SUCCESS)
  • 100 (Network error)
  • 200 (Source file system error)
  • 300 (Target file system error)
  • 400 (General failures)
  • Added autocomplete to the Connect bar in the toolbar, which makes finding and connecting to saved sessions easier.
  • Multiple sessions can be dragged and dropped or copied and pasted in the Session Manager and Connect dialog.
  • A new global option "Sort folders at top" forces the folders always to be sorted at the top of the local and remote windows regardless of which column is used for sorting and whether the order is ascending or descending. This option is on by default for new installations.
  • SSH2: Added support for the ChaCha20/Poly1305 cipher.
  • SSH2: Added support for the AES-GCM cipher.
  • SSH2: Added support for the UMAC-128 MAC algorithm.
  • Added the ability to use OpenSSH certificates for authenticating SFTP sessions.
  • SSH2: Added a new session option "Use a separate transport for every connection," which establishes a new SSH2 transport for every parallel SFTP transfer.
  • SFXCL: Added a new option /ReconnectDelay, which allows the number of seconds between losing a connection and the initial reconnect attempt to be specified.
  • Windows: Added an Administrative Policy option to disconnect sessions authenticated using CAPI/PKCS#11 when the corresponding smart card is removed.
  • Changes:
  • Filtered searches in the Session Manager and Connect dialog could be very slow when the session database contained thousands of sessions.
  • In the Transfer queue, when the filename or destination is a remote system, the hostname is prepended.
  • The option for displaying hidden files in the local window can be toggled from the View menu.
  • If the global option "Show Session Manager or Connect dialog on startup" is set, the Session Manager is displayed when SecureFX starts. Previously, only the Connect dialog honored this option.
  • SSH2: Modified the default authentication order to be PublicKey, Keyboard Interactive, Password, and GSSAPI. This only affects new installations.
  • The default session filter delay has been changed from 500 milliseconds to 250 milliseconds. This only affects new installations.
  • Up to 20 sessions can be included on the recent session list.
  • SSH2: If a session is using public-key authentication and the key file has not specified, the user is no longer prompted to specify the file.
  • SSH2: When importing an SSH2 host key, if it's possible to extract the hostname, IP address, and port from the filename, those values will be used as the default values. Otherwise, the default value for port will be set to 22 and the other values will be left blank.
  • SSH2: Pressing the SHIFT key in the New Host Key dialog allows a host key to be saved once.
  • SSH2: In the dialogs that prompt to accept the host key, the SHA-2 fingerprint is also displayed in base64.
  • In the View Host Key dialog, SHA-2 fingerprints are displayed in base64 in addition to hexadecimal.
  • When being prompted to accept an SSH2 host key, the fingerprints are now shown in a separate dialog.
  • SSH2: The trace output shows the SHA-2 host key fingerprint as base64 in addition to hexadecimal.
  • The username used for authentication is now logged in the trace output.
  • SecureFX uses a templated path, which gets modified to an appropriate path on each platform, for the global option "Log File V2".
  • If SecureFX is launched using the -F command-line parameter or is on a USB drive, the actual configuration path being used is shown in the Global Options dialog.
  • Bug fixes:
  • In the New Session wizard and the Quick Connect dialog, once a session was selected as the Firewall, "Select Session..." was no longer in the Firewall dropdown list.
  • When uploading a file to a Cisco iOS device, a prompt was displayed if the file did not exist in the target folder.
  • File transfers to a Cisco ASR9K router using SCP failed because SecureFX sent an extra "cd" command, which made the wrong directory the current directory.
  • The transfer queue displayed "Could not retrieve error text for error code 0xe000001c" when an upload failed due to a disk space error.
  • A session that contained spaces could not be connected from the Connect bar using the /S flag.
  • Windows: If the Connect bar was showing a dropdown list, pressing ALT+Q displayed the Quick Connect dialog, but did not put focus there.
  • Windows: On high-DPI monitors, the EULA dialog in the installer did not display correctly.

New in SecureFX 8.1.4 Build 1443 (Aug 10, 2017)

  • Changes:
  • SFXCL: Added a global INI-file-only option called "SFXCL Backslashes Always Path Separators". When this option is on, backslashes in
  • SFXCL command-line paths are replaced with forward slashes. This option restores the version 7.3 behavior
  • Bug fixes:
  • SecureFX crashed when a session specified %USERNAME% as the username and specified another session as the firewall, then authentication failed and the username was changed to something other than %USERNAME%
  • SecureFX could crash when an FTP connection was established if the initial attempt failed because cleanup was done on the wrong socket
  • SecureFX could crash if multiple imports of settings ran at the same time
  • When the configuration folder was being stored in the cloud using services like OneDrive or Dropbox, duplicate copies of FolderData__.ini could be created and appear as sessions in the Session Manager or Connect dialog
  • When SecureFX was integrated with SecureCRT, if SecureFX was launched from the command line or Quick Connect, it always used SFTP as the protocol even if the default session specified a different protocol
  • PKCS #11 authentication failed when using the SuisseID PKCS #11 DLL
  • Windows: When "Update Now..." was selected from the Help menu, if a newer version was available, the installer was downloaded to the parent folder of %TEMP%

New in SecureFX 8.1.3 Build 1382 (Aug 10, 2017)

  • Bug fixes:
  • Authentication failed when attempting to authenticate using a smart card that contained multiple certificates with blank "Issued to" and "Issued by" fields.

New in SecureFX 8.1.2 Build 1362 (Apr 28, 2017)

  • Bug fixes:
  • SecureFX crashed when attempting to load a certificate from a TIKS card that was inserted in an internal reader.
  • File uploads to ProFTPD with TLS enabled could hang due to the way SecureFX handled the remote system's TLS shutdown packet.
  • Certificate chaining failed for RFC 6187 when using PKCS#11 if the complete chain of certificates was not on the smart card.
  • When performing X.509 authentication to an OpenSSH server with Roumen Petrov's PKIX patch applied, the wrong hashing algorithm was used for generating the signature for an RSA certificate.
  • Windows: SSH agent did not use the algorithm name specified by RFC 6187 if the session used an X.509 certificate stored in a file.

New in SecureFX 8.1.1 Build 1319 (Feb 28, 2017)

  • Bug fixes:
  • In the New Session wizard, when a hostname was entered as uppercase it was changed to lowercase when it was saved. The case of the hostname as entered is now preserved
  • SFXCL: SFXCL could crash if an FTPS session could not find the specified TLS certificate or if the TLS certificate was passphrase protected
  • Windows: Scheduled tasks were not included in the XML file when settings were exported from Windows 7, Server 2008 R2, and Server 2012 R2

New in SecureFX 8.1 Beta 5 (Jan 18, 2017)

  • Bug fixes:
  • ECDSA keys with bit sizes of 384 or 521 generated by SecureFX could
  • not be added to ~/.ssh/authorized_keys using ssh-keygen.
  • If a local file was copied and pasted into a remote folder specified
  • in the path bar and then deleted and pasted into the remote session
  • again, it was pasted into the parent folder.
  • SecureFX did not display symbolic links when the remote system was a
  • ProFTP server.
  • Mac: If a session name contained two or more ampersand characters,
  • when the session name was shown in the File or Window menu, it had
  • at least one extra ampersand.

New in SecureFX 8.1 Beta 4 (Dec 20, 2016)

  • Bug fixes:
  • If a remote file was edited and was saved while SecureFX was minimized, the file did not get uploaded until the mouse cursor hovered over SecureFX or SecureFX received focus.
  • If an FTP session contained a local shell command pre-connect string that was an invalid command, SecureFX crashed when attempting to connect to the session.
  • SSH2: If an RSA key was generated and the .pub file was specified to be used as a raw SSH2 key for public-key authentication, a format error was reported during authentication.
  • Windows: The installer option "Subscribe to Product Announcements" did not work.

New in SecureFX 8.0.4 Build 1252 (Dec 6, 2016)

  • Bug fixes:
  • When the session database contained several folders, if the settings were exported and then imported into an empty configuration, the folders were not in alphabetical order.
  • The Session Manager and Connect dialog showed the expansion icon on an empty folder if the folder previously contained sessions.
  • SSH2: SecureCRT crashed when attempting to use the ECSA certificate from a Yubikey smart card.
  • SSH2: SecureFX reported an error when attempting to connect to a Cisco device that used the ident string "SSH-2.99-Cisco-1.25".
  • Windows: On a high-DPI monitor scaled to 150%, some of the controls on the Keyboard Interactive dialog were cut off.
  • Windows: The menu font in SecureFX was different from SecureCRT's.

New in SecureFX 8.1 Beta 3 (Dec 2, 2016)

  • New features:
  • Windows: Added preliminary support for certificate chaining for RFC 6187 when using CAPI.

New in SecureFX 8.1 Beta 2 (Dec 2, 2016)

  • Bug fixes:
  • If the host key database was on a network share and contained thousands of keys, there was a delay when attempting to display the Global Options dialog.
  • If a file was copied from the desktop and pasted into a remote session in SecureFX and was then deleted on the remote server and pasted again in SecureFX, the remote file listing did not get updated.

New in SecureFX 8.1 Beta (Oct 28, 2016)

  • SecureFX for Mac has a new GUI and main toolbar. Mac and Linux versions have new toolbar icons in the Session Manager and Connect dialog.
  • A “Synchronize File Browsing” option allows lockstep navigation of local and remote folders that have the same directory structure.
  • Server-to-server synchronization makes it easier to roll out changes to a production server, do backups, and do replication.
  • Enhanced smart card (PIV/CAC) support is now available on all platforms. Select a specific certificate on the smart card (PIV/CAC) to be used for public-key authentication. PKCS #11 certificates are supported. The username can be pulled directly from the specified certificate.
  • The Options menu now includes an “Edit Default Session” item so you can quickly change the default session and the Session Manager and Connect dialog right-click menus now include “Expand All Folders” and “Collapse All Folders”.
  • SFXCL enhancements include a /ConfigPassphrase option for specifying a configuration passphrase on the SecureFX and SFXCL command line and a /NoTempFiles option that prevents the creation of temporary files during synchronize and quick synchronize operations.

New in SecureFX 8.0.3 Build 1183 (Sep 9, 2016)

  • Bug fixes:
  • SecureFX crashed when attempting to export settings that contained a session with a blank name
  • SecureFX/SFXCL did not wait to receive the 221 response from the server after sending a QUIT, which could result in the control connection not being closed cleanly
  • Windows: When toggling between new and legacy display themes SecureFX could get in a state where the application toolbar contained the new icons and the menus contained the legacy icons or vice versa

New in SecureFX 8.0.1 Build 1082 (Apr 26, 2016)

  • Changes:
  • Pressing ALT+M will open the Session Manager if it's hidden
  • Pressing ALT+I will display the Session Manager if it's hidden and put focus in the filter bar
  • Windows: SecureFX now uses the proper default action (Open or Edit) associated with file types in the system settings in order to work better with editors such as EmEditor
  • Bug fixes:
  • The fallback mechanism for public-key authentication did not work correctly and authentication failed rather than prompting for the username and public key
  • When connecting to multiple sessions, the Local window was moved to a different tab group
  • If SecureFX did not open any local or remote windows on startup and auto-hide was on for the Session Manager, the Session Manager stayed open
  • Fixed a memory leak that occurred when ECDSA keys were used

New in SecureFX 8.0.0 Build 1063 (Mar 31, 2016)

  • Bug fixes:
  • SFXCL: When multiple SFXCL processes were launched simultaneously, SFXCL could prompt for a configuration passphrase even when no passphrase was used.

New in SecureFX 8.0.0 Build 1055 Beta 5 (Mar 22, 2016)

  • Bug fixes:
  • If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, settings could not be saved in the personal data folder even though it was writable.
  • If the configuration paths were set up so that a personal data folder was being used and the configuration folder was read-only, attempting to merge the configuration data failed and the personal data was deleted.

New in SecureFX 8.0.0 Build 1045 Beta 4 (Mar 21, 2016)

  • New feature:
  • When setting up a synchronize operation, the remote folder can be browsed
  • Changes:
  • The Session Manager's "auto hide" option is on by default
  • Windows: The mouse scroll wheel can be used when hovering over a UI element such as the list view or tree view without having to click first

New in SecureFX 8.0.0 Beta 2 (Feb 25, 2016)

  • Changes:
  • Added the ability to disable scheduled tasks.
  • Bug fixes:
  • When running an FTPS synchronization operation with a lot of remote files, the operation eventually failed with a "Connection terminated abnormally" error during a SIZE command.
  • An error string was displayed in the "Files of Type" field in the Select File to Upload dialog.

New in SecureFX 7.3.7 Build 1034 (Feb 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

New in SecureFX 8.0.0 Build 1011 Beta 1 (Jan 29, 2016)

  • New features:
  • Windows: Added the ability to schedule transfer and synchronize operations. The frequency can be once, daily, weekly, or monthly and SecureFX does not need to be running
  • Windows: The user interface has new themes and new toolbar icons
  • Windows: Updated the icons used in the remote view
  • Added the ability to create a file on a remote system
  • Added the ability to use and generate ECDSA (RFC 5656) and Ed25519 keys
  • Added the ability to generate keys in the new OpenSSH format
  • SSH2: PuTTY PPK keys can be used for public-key authentication
  • SSH2: On Windows, enhanced public-key authentication to allow a public key to be specified from the CAPI or PKCS #11 store
  • SSH2: On Windows, public keys can be exported in OpenSSH format and can be exported from PKCS #11
  • SSH2: On Windows, added support for X.509 authentication using the x509v3-ssh-rsa and x509v3-ssh-dss algorithms as specified in RFC 6187
  • SSH2: On Windows, certificates can be used as a raw key for public-key authentication
  • SSH2: On Windows, X.509 v3 keys can be added to the SSH agent
  • Changes:
  • The ability to use a session as a firewall has been added to the Quick Connect dialog and the Session wizard
  • Quick Connect sessions that are saved are put in the current folder in the Session Manager
  • ID numbers shown in the log file for transfer, synchronize, and file operations are now unique
  • The format of some log messages was changed as shown below "Session established for synchronize with " changed to "Operation established for synchronize with "
  • "Synchronize(): sfxcl version ()" changed to "sfxcl version ()"
  • "Session established for session " changed to "Session window established for session "
  • "Session established for address " changed to "Session window established for address "
  • "Session(00000000): sfxcl version ()" changed to "sfxcl version ()"
  • Changed the SSL GUI protocol names to "FTP/TLS (implicit)" and "FTP/TLS (explicit)" to reflect that TLS is supported
  • Added "Contact Support" to the Help menu
  • SSH2: If host key authentication fails with the ssh-dss algorithm the ssh-rsa algorithm is preferred on subsequent attempts to reconnect the session
  • SSH2: It's now possible to specify the minimum group exchange prime size in the Session Options dialog
  • SSH2: The "diffie-hellman" key exchange algorithm is off for the default session. This change only affects new installations
  • SSH2: SHA-1 and SHA-2 fingerprints are displayed for public keys in addition to MD5
  • SSH2: In all places where the host key fingerprint is displayed the SHA-2 fingerprint is also displayed
  • SFXCL: Host key messages are now logged
  • SFXCL: When the remote server is WS_FTP and the protocol is SFTP trailing slashes are stripped from paths
  • Windows: If the administrative policy "Enable Check For Updates" is set to false, "Update Now" is not allowed
  • Bug fixes:
  • Attempting to delete a session without a name caused every session in the session database to be deleted
  • SecureFX could become unresponsive when settings were being imported or exported, especially when the configuration was large e.g., lots of sessions)
  • SecureFX could not connect to an FTPS server that requested a client certificate without specifying a client certificate, which is allowed by SSL and TLS
  • SFTP: If a binary file was transferred to a Globalscape server with compression set to zlib, the file could be corrupted
  • SFTP: Files could be corrupted when multiple files were downloaded from an SFTP server if the maximum number of parallel transfers was set to a value larger than 1 and the transfer queue was being used
  • SFTP: SecureFX did not work with MikroTik routers running RouterOS
  • SSH2: If the host key database was on an offline cached network drive, SecureFX was not able to save new host keys
  • SSH2: The cached session password was not updated after a password change was forced by the remote system
  • SFXCL: If multiple files were transferred and one or more files failed to transfer, but one or more files transferred successfully
  • SFXCL returned a success exit code
  • Windows: When the session database contained folders and one of those folders was deleted in the Session Manager, if a session was created using the Quick Connect dialog, the session was not saved in the selected folder and any expanded folders were collapsed
  • Windows: On high-DPI monitors with scaling enabled, folders in the Session Manager and local and remote windows could not be expanded or collapsed

New in SecureFX 7.3.6 Build 963 (Dec 2, 2015)

  • Bug fixes:
  • The New Session wizard reported an error when an IPv6 address was entered as the hostname.
  • 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.

New in SecureFX 7.3.5 Build 903 (Sep 11, 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."

New in SecureFX 7.3.4 Build 839 (Jun 17, 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.

New in SecureFX 7.3.3 Build 779 (Apr 1, 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 requires 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.

New in SecureFX 7.3.2 Build 752 (Feb 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.

New in SecureFX 7.3.1 Build 685 (Dec 5, 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.

New in SecureFX 7.3.0 Build 657 (Oct 24, 2014)

  • Bug fixes:
  • SecureFX crashed when attempting display the information for an incorrectly formatted SSH host key.
  • Selecting the "Update Now" menu item did not reset the clock used to check for updates every 30 days.

New in SecureFX 7.3.0 Build 642 Beta 5 (Oct 3, 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.

New in SecureFX 7.3.0 Build 633 Beta 4 (Sep 24, 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.

New in SecureFX 7.3.0 Build 622 Beta 3 (Sep 10, 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.
  • 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.

New in SecureFX 7.3.0 Build 611 Beta 2 (Sep 5, 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.

New in SecureFX 7.2.6 Build 606 (Aug 20, 2014)

  • Bug fixes:
  • Server-to-server transfers could hang if hostname resolution was required for both remote systems.
  • If the transfer queue was used and a substitute user operation had been executed, transfers did not start until the remote connection was refreshed.
  • The Session Manager and Connect dialog scrollable area was not large enough to show all sessions after expanding a folder that contained several sessions.
  • SFXCL: If multiple files were transferred in the same operation and a failed transfer preceded a successful transfer, SFXCL reported that the entire transfer operation was successful.

New in SecureFX 7.3.0 Build 597 Beta 1 (Aug 8, 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.
  • 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.
  • 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.

New in SecureFX 7.2.5 Build 550 (Jun 6, 2014)

  • Bug fixes:
  • The Connect dialog did not have a horizontal scrollbar.

New in SecureFX 7.2.4 Build 524 (May 2, 2014)

  • Changes:
  • In the Session Options dialog, the width of the Firewall dropdown was increased in order to accommodate long names.
  • Bug fixes:
  • If a license was validated with an issue date that contained an en dash or em dash, SecureFX crashed when the About box was displayed.
  • SFXCL: If logging was specified and a transfer was attempted to a folder that did not exist, the log reported the error, but did not report the correct folder.

New in SecureFX 7.2.3 Build 500 (Apr 2, 2014)

  • Bug fixes:
  • When sessions were sorted using the option to arrange the tree logically, the sessions were not sorted correctly
  • In the Quick Connect dialog, if options such as "Show quick connect on startup" or "Save session" were changed and then the dialog was cancelled, the options were saved

New in SecureFX 7.2.2 Build 491 (Mar 20, 2014)

  • Bug fixes:
  • If the session manager was unpinned and then closed, the area in the local or remote window where the session manager had been no longer scrolled.
  • The Quick Connect dialog was not displayed at startup when the option "Show Quick Connect at startup" was set.
  • SFXCL: An error was not reported when a transfer operation failed because the source file or folder did not exist.
  • SFXCL: If the source file started with a "/" character, the transfer summary could report that more files succeeded than were attempted.
  • Windows 8: SecureCRT crashed when attempting to upload or create a new key using the public-key assistant.
  • Mac: The "Punctuated" number style global option did not work.
  • Changes:
  • Added a new session INI-file-only option "Disable Initial SFTP Extensions", which allows the fs-multiple-roots-supported request to be disabled for compatibility with servers such as nuBridges.

New in SecureFX 7.2.1 Build 443 (Jan 17, 2014)

  • Bug fixes:
  • If a synchronize operation was stopped and then restarted, the file status was changed to "queued", but the transfer did not resume.
  • If a synchronization operation specified an invalid remote path, SecureFX incorrectly reported that the synchronization operation succeeded.

New in SecureFX 7.2.0 Build 415 (Dec 23, 2013)

  • Bug fixes:
  • If a large transfer was in progress and the local window was opened and closed several times and then the transfer was cancelled, SecureFX could crash.

New in SecureFX 7.2 Beta 5 (Dec 23, 2013)

  • Bug fixes:
  • SecureFX crashed if a password for a session that displayed an authentication banner at logon was changed in the Session Options dialog when the session was not connected.
  • Deleting a symbolic link on the remote system deleted the original file or folder rather than the link.
  • SCP: Symbolic links were not resolved correctly, which meant that it was not possible to navigate into a symbolic link that was a folder.

New in SecureFX 7.2 Beta 4 (Dec 23, 2013)

  • Changes:
  • When the session list is empty and the option "Show the connect dialog at startup" is set, the Quick Connect dialog is displayed at startup.
  • Bug fixes:
  • Windows: Resetting the main toolbar caused the customize button to disappear.

New in SecureFX 7.2 Build 384 Beta 3 (Nov 7, 2013)

  • Changes:
  • A progress indicator is displayed when personal data is being separated or merged.
  • Added support for the format of directory listings from the Glub Tech Secure FTP Wrapper.
  • SSH2: The length of the Secure Shell identity string was reduced in order to be compatible with non-compliant servers.
  • If the session manager is pinned or is a modeless window, pressing ALT+C when focus is not in the session manager sets focus to the session manager.
  • If the global option "Use dockable session manager" is toggled, a restart of SecureFX is not required for the change to take effect.
  • Bug fixes:
  • SecureFX crashed if it was closed while a synchronize operation was comparing files.
  • The personal data folder option did not honor environment variables.
  • If the session manager had focus and SHIFT+DELETE was pressed, the delete event was sent to the local or remote window, which could cause a file or folder to be inadvertently deleted.

New in SecureFX 7.2 Build 372 Beta 2 (Oct 23, 2013)

  • New features:
  • Added autocomplete support to file and directory edit fields in all dialogs.
  • Changes:
  • The default order of the SHA2 MAC algorithms was changed so that SHA2-512 comes before SHA2-256. This only affects new installations.
  • Bug fixes:
  • If the number of parallel transfers was set to 5 and "Cancel All" was selected from the Transfer Queue menu while a directory with a lot of files (>1000) was being uploaded, SecureFX crashed.
  • When the "Maximum number parallel transfers" option was set to two or more and at least two files were moved, the source files were not removed.
  • Scrolling the sessions in the Connect dialog or session manager (Windows) was significantly slower than in versions prior to 7.2.
  • When the session manager was docked and unpinned, if SecureFX started in a state where there was no local or remote window open, the keyboard accelerator to access the session manager did not work.
  • When the session manager was docked and unpinned, if focus was moved from the session manager to the session or command window using a keyboard accelerator, the session manager was not hidden.
  • If the session manager was docked and unpinned and ALT+C or ALT+B was pressed, the session manager was shown and then immediately hidden.
  • If the session manager was docked and unpinned and then closed, when an action to connect to a session, such as pressing the Connect toolbar button, was performed, the session manager was shown and then immediately hidden.
  • If the session manager was docked and unpinned and then closed, the next time SecureFX started, the session manager was shown and had focus.
  • Changing the theme from a theme other than "Shaded" back to "Shaded" caused a dropdown arrow icon to be drawn on the session manager title bar.

New in SecureFX 7.2 Build 359 Beta 1 (Oct 23, 2013)

  • New features:
  • 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 SCP support for Cisco and Juniper devices.
  • Added a global option to store personal data such as usernames and passwords in a location separate from the rest of the session data, which allows personal data to be kept private while other configuration data is stored on a network drive or on the cloud so that it can be used on different systems or shared with colleagues.
  • Added a new synchronization option called "Automatically transfer files", which causes files to be synchronized automatically when the Synchronize dialog/tab is opened. The files will also be monitored and transferred automatically while the Synchronize dialog/tab is open.
  • Added a global option "Use this type for all files", which allows ASCII or binary to be forced for every transfer.
  • Added a right-click menu item "Add Bookmark", which provides a quicker way to bookmark folders.
  • Added a right-click menu item that creates a new folder in the current folder.
  • In order to comply with Section 508 Accessibility, there are two new ways to access the transfer queue: Added the accelerator ALT+G and added an item to the Edit menu that toggles between "Go To Transfer Queue" and "Go To Session Window".
  • SSH2: Added support for SHA-2 MAC algorithms.
  • Changes:
  • The authentication banner is now displayed in the log view instead of in a pop-up dialog.
  • Error dialogs are no longer displayed in the transfer queue when a transfer fails.
  • Added "Copy Filename" to the right-click menu.
  • Bug fixes:
  • If a new session was created and the password was saved, the password had to be re-entered if the session was connected again without disconnecting the original session.
  • In the Synchronize tab/window, the right-click menu items "Synchronize Source-Only Items", "Synchronize Target-Only Items", etc. were not being honored.
  • If the keyboard was used to bring up the Transfer Queue context menu, the menu was displayed in the upper left corner of the monitor.
  • SSH2: If a server was configured to require multiple authentication methods and the server did not update the continuations list after a partial success, SecureFX did not move on to the next authentication method.

New in SecureFX 7.1.2 Build 316 (Aug 9, 2013)

  • Bug fixes:
  • SecureFX crashed when an FTP session using PORT and connecting through a SOCKS version 5 firewall was closed.
  • If the tree view was active and then hidden, SecureFX crashed the next time it started.
  • In the "Properties" dialog, when typing into the "Attributes" field, the cursor always stayed on the left side, causing text to be entered backwards.
  • In the "Properties" dialog, the "Size" field showed the size in the same units twice rather than in larger and smaller units, such as KB and bytes.
  • SFXCL: If a file had no attributes, the log file incorrectly reported that two transfer attempts were made instead of one.

New in SecureFX 7.1.1 Build 264 (May 31, 2013)

  • Bug fixes:
  • SecureFX could crash when transferring a large number of files into the current directory of the local window.
  • Windows: SFXCL: The "no-subdir" option was not honored when using "/QuickSync".

New in SecureFX 7.1.0 Build 244 (May 3, 2013)

  • Bug fixes:
  • If the global option "Display filenames using Explorer attributes" was set and the ESC key was pressed while a file on the local system was being renamed, SecureFX crashed.

New in SecureFX 7.1.0 Build 230 Beta 4 (Apr 12, 2013)

  • Bug fixes:
  • SecureFX could crash if a transfer was in progress when the session's connection was lost (e.g., the remote system went down).
  • The "Upload" menu item in the right-click menu was incorrectly disabled if an upload was in progress.

New in SecureFX 7.0.4 Build 537 (Apr 4, 2013)

  • Bug fixes:
  • If a session password had been saved and then the administrative option disallowing saved passwords was set, when connecting to the session with the saved password, the password field in the password prompt contained the masked password instead of being blank.

New in SecureFX 7.1.0 Build 208 Beta 2 (Mar 15, 2013)

  • Bug fixes:
  • Dependent session firewalls only worked when SecureFX was integrated with SecureCRT.
  • The authentication prompt was displayed every time a host disconnected and reconnected, which resulted in multiple authentication prompts being displayed when authentication timed out.
  • When SecureFX was integrated with SecureCRT, if a dependent session firewall was specified and then the session protocol was changed, the firewall field did not get updated on the protocol page.

New in SecureFX 7.1.0 Build 195 Beta (Mar 15, 2013)

  • New features:
  • Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.
  • SSH2 on Windows: Added support for SHA1 in RSA signatures, which allows X.509 certificates to be used in FIPS mode and other settings where MD5 cannot be used.
  • Changes:
  • The limit on parallel transfers has been adjusted so that it's possible to have more than eight.
  • Bug fixes:
  • If a time change occurred (e.g., daylight savings time) while a synchronize operation was active, the file status information was incorrect.
  • On a remote system that hides file extensions, if a file was renamed, the file extension was removed.
  • The log file did not report the correct directory when an open directory failed.
  • UTF-8 encoded characters were not displayed properly in the SecureFX log.
  • SecureFX displayed garbage characters for the session name in the log when the recently used session list was used to connect to the session.
  • In the "Connect" dialog, if a new folder was given the same name as an existing folder except for different capitalization, after exiting and restarting SecureFX, both folders were gone.
  • It was possible to add a blank file type.
  • SCP: If a directory had more than nine links, it was not displayed in the file list.
  • Windows: SecureFX did not honor the "Display filenames using Explorer
  • attributes" global option.
  • Windows: The application icon was not removed from the Program group during an uninstall.

New in SecureFX 7.0.3 Build 480 (Jan 18, 2013)

  • Bug fixes:
  • In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted.
  • SFXCL: If a wildcard pattern started with "*" and contained multiple wildcards, the match results were not correct.

New in SecureFX 7.0.2 Build 418 (Oct 26, 2012)

  • Bug fixes:
  • SecureFX crashed if a firewall was specified on the command line and the firewall was not configured.
  • SecureFX either crashed or hung when attempting to upload a key through the Quick Connect dialog.
  • SecureFX could crash when a session was disconnected while connected to the remote system over a VPN.
  • On a system that had two monitors with the primarary monitor having a larger display resolution than the secondary monitor, when SecureFX was maximized on the primary monitor and then restored, it used the resolution of the secondary monitor.

New in SecureFX 7.0.1 Build 374 (Aug 30, 2012)

  • If the local window option "Position on bottom/right when tabbed horizontally/vertically" was set and the local window was toggled off, on, and back off again, SecureFX crashed.
  • SecureFX could crash after some changes were made in the Global Options dialog and then SecureFX was restarted.
  • Toggling the local window twice caused the local and remote sessions to appear in a single tab group.
  • When SecureFX and SecureCRT were integrated, if the configuration folder contained "%APPDATA%", attempting to launch SecureCRT from the SecureFX toolbar caused an error to be reported.
  • FTP: When downloading a file from a Solaris FTP server, SecureFX hung at the end of the transfer.

New in SecureFX 7.0.0 Build 307 Beta 3 (Jun 6, 2012)

  • When the SecureFX window was resized, it flickered.

New in SecureFX 7.0.0 Build 295 Beta 2 (May 23, 2012)

  • Changes:
  • When the Date column is selected in a local or remote session window, the sort order is now descending instead of ascending.
  • Bug fixes:
  • SFXCL: When files were transferred using the /Move option, no error was reported if a source file could not be deleted.

New in SecureFX 7.0.0 Build 281 Beta 1 (May 4, 2012)

  • New features:
  • Added a filter control that supports wildcards to the session toolbar, which makes it easier to find specific folders and files in local and remote sessions.
  • After a synchronize operation, the synchronize file list is automatically refreshed when changes are made to files on the local system, which allows files to be re-synchronized without having to close the synchronize tab.
  • A refresh button was added to the synchronize view, which allows files to be re-synchronized after the initial synchronization.
  • Bookmarks can be opened directly from the right-click menu in local and remote sessions and from the "File" menu.
  • Added a global option to position the local window at the bottom or right when SecureFX is tabbed horizontally or vertically.
  • SFXCL: Added the ability to specify explicit FTPS on the command line as "ftpes://".
  • SSH2: Added the ability to skip authentication methods while authenticating.
  • Changes:
  • Improved the performance of synchronization operations involving a large number of files.
  • SecureFX will continue connecting when either of the initial PBSZ or PROT commands fails, in compliance with Note 1 in section 12.1 of RFC 4217.
  • In the Synchronize view, the information in the "Last Action" column for transfers was changed to specify whether the transfer was an upload or download.
  • The synchronize view columns were modified so that the current status and last action are shown.
  • It is no longer possible to add duplicate bookmarks.
  • The "Open Bookmarks" dialog was renamed "Manage Bookmarks".
  • FTPS: SecureFX now logs server-to-server file transfer failures.
  • SFXCL: Added a command-line option "/Chmod", which provides the ability to change permissions of remote files.
  • SFXCL: SFXCL returns the error code for file not found if a wildcard is specified and there are no matches.
  • Bug fixes:
  • After browsing to a folder with a large number of files (> 35,000) and then cancelling the listing, SecureFX could crash.
  • Synchronization operations that accessed UNC shares failed on Windows Server 2008 R2.
  • Double-clicking a local file resulted in an error if the file type was associated with an editor such as EmEditor.
  • It was not possible to navigate to a remote folder where the group name contained a space.
  • If values for "Remote ListView State" were garbage, it caused the columns in the "Details" view to be displayed incorrectly.
  • If a transfer that caused the choose transfer type and overwrite prompts to be displayed was started and the network disconnected while the first prompt was displayed and then the session reconnected, the second prompt was not displayed and the file was overwritten.
  • The "Quick Connect" dialog sometimes used the default username or previously used username even though the username was empty.
  • Double-clicking a bookmark in the "Open Bookmark" dialog did not open the bookmark.
  • The DELETE key could not be used to delete a bookmark in the "Open Bookmarks" dialog.
  • If more than one instance of SecureFX was running, changes made through the "View" menu were not propagated to the other instance(s).
  • SecureFX created a registry structure for configuration information when the configuration folder was specified on the command line using "/F".
  • FTP/FTPS: SecureFX file transfer operations stalled if a 526 error was received from the remote system.
  • FTP: While attempting to connect to an FTP server using an HTTP proxy and PASV data connections, if SecureFX was unable to obtain the peer address from the control connection, it crashed.
  • FTP: When an FTP session connected to 127.0.0.1, the machine's actual IP address was used for the PORT command instead of 127.0.0.1.
  • SSH2: Authentication failed when the server requested the keyboard-interactive method more than once.
  • SFXCL: On servers that stored timestamps in seconds rather than milliseconds, when the "Overwrite older" flag was specified, identical files were uploaded again.
  • Windows: With tabs off, when a local or remote window was minimized and then selected from the Windows 7 task bar, the restored window was not painted correctly.
  • Windows: In the Chinese version of Windows XP and Vista, the font used for the title bar, menu, and status bar was smaller than the system font.

New in SecureFX 6.7.4 Build 354 (Feb 3, 2012)

  • Bug fixes:
  • SecureFX crashed if files were dragged to a session that was not
  • fully connected
  • Passwords saved prior to administratively prohibiting saving
  • passwords were still present
  • The PORT connection (FTP) incorrectly logged port 0 for the
  • control connection

New in SecureFX 6.7.3 Build 292 (Nov 10, 2011)

  • Changes:
  • SFTP/SCP: SecureFX could not connect to a Pragma Fortress SSH server, because this server does not support SFTP extensions. SFTP extensions are now automatically disabled for this server.
  • Bug fixes:
  • When connecting to a session through a firewall, the username and password were prompted for even though they were specified in the proxy setting.
  • In the context menu, in the "Go To" pull-right menu, the "Forward" item was never available.
  • FTP: Attempting to connect to an FTP session that used PASV data connections through an HTTP proxy could cause SecureFX to crash.
  • SFXCL: SFXCL crashed when a /Quicksync mirror operation that deleted a file from the local system was performed.

New in SecureFX 6.7.2 Build 229 (Aug 12, 2011)

  • Changes:
  • The 32-bit installer can be installed on a 64-bit system.
  • Bug fixes:
  • On a 64-bit machine, if SecureFX was launched from the SecureCRT toolbar and was closed using the red "X", SecureFX could crash.
  • The Connect dialog allowed connect attempts to sessions with the protocol set to "None".
  • The extend evaluation feature did not work correctly. After the offer was accepted, there was no button to extend the evaluation on the "Enter License" dialog as described in the instructions that had been e-mailed.
  • SFXCL: The SFXCL command-line could not contain a ";" character
  • in a the destination filename.

New in SecureFX 6.7.1 Build 188 (Jun 17, 2011)

  • Bug fixes:
  • In the Quick Connect dialog, if the port number was changed to something other than the default, the port number was reset to the default the next time the Quick Connect dialog was opened.
  • Windows: When the Windows 7 Areo snap feature was enabled, if the SecureFX window was dragged so that it snapped to the side of the desktop and focus was switched to another application, when SecureFX was restored from the taskbar, it reverted to its previous size.

New in SecureFX 6.7.0 Build 172 (May 27, 2011)

  • Bug fixes:
  • On Windows 7, if the log view for a remote session was resized so that it was not visibile and the remote session window was selected from the Windows taskbar, the log view was restored to its previous size.
  • FTP/FTPS: SecureFX crashed when attempting to connect to sessions where PASV connections would be blocked by a firewall.

New in SecureFX 6.7.0 Build 164 Beta 5 (May 19, 2011)

  • Bug fixes:
  • On Windows 7, if Maximize was selected for a SecureFX window displayed in the taskbar popup, a separate window was displayed outside the SecureFX window and SecureFX sometimes crashed.
  • During a synchronize operation, the Status information was cleared
  • immediately after files were transferred.
  • When a folder upload was canceled and the transfer queue was off and a file had been skipped because it already existed on the remote system, if the transfer was later resumed, the first file that had been skipped previously was transferred.
  • When tabs were disabled, the icon displayed in the title bar of the windows was a generic icon instead of the SecureFX application icon.

New in SecureFX 6.7.0 Build 153 Beta 4 (May 5, 2011)

  • Bug fixes:
  • If a transfer was cancelled while multiple files were being downloaded and then the session was closed and reconnected, attempting to resume the transfer caused SecureFX to crash.
  • SecureFX menu customizations were sometimes not saved.
  • When the /F parameter was used on the command line to specify the location of the configuration folder and the menu or toolbar was customized, the changes were not saved.
  • FTP: SecureFX could crash when a folder was being uploaded due to the way Send requests were handled.

New in SecureFX 6.6.3 Build 412 (Apr 26, 2011)

  • SecureFX crashed after selecting "Cancel Selected" in the transfer queue if any of the selected items were no longer being transferred.
  • If a connection was lost during a transfer and the transfer was cancelled and then focus was set to another window while the session was attempting to reconnect, SecureFX crashed.
  • After a transfer progress tab closed, focus was not set to the correct session tab.
  • The keyboard accelerator SHIFT+INSERT did not paste text into the session address bar.
  • SFTP: SecureFX crashed if an SFTP upload overwrote a file owned by someone else.

New in SecureFX 6.7.0 Build 137 Beta 3 (Apr 13, 2011)

  • Bug fixes:
  • If the menu items "Add Bookmark" or "Open Bookmark" were added to the toolbar through customization and then were clicked after connecting to a host, SecureFX crashed.
  • If a session that used a firewall was connected and disconnected and then the session was modified to use a different firewall and then reconnected, the old firewall was used.
  • If the display of the Connect bar was toggled from the View menu and then modified in the Global Options dialog, the change in the Global Options dialog was not honored.
  • If files were dragged from Windows Explorer into an empty local folder in SecureFX, the view was updated, but not all the files that had been dragged over were displayed.
  • If a synchronize session's direction was set to "Mirror local" and then was changed to "Mirror remote", the direction was not displayed correctly in the Synchronize Session Properties dialog even though the correct direction was used for the synchronize operation.
  • After pressing the ALT key and then the ENTER key, SecureFX attempted to connect to a host named "".

New in SecureFX 6.7.0 Build 123 Beta 2 (Mar 25, 2011)

  • New time-saving options:
  • Bookmarks: Set and reuse bookmarks to save time accessing regularly used directory locations, especially if directories are several levels deep.
  • Connect bar: Use a text entry box on the toolbar to quickly connect new sessions without having to open a dialog. The Connect bar supports command-line options for maximum flexibility.
  • Logical sort for Connect dialog: Option to sort sessions logically in the Connect dialog, which is useful when session names contain numbers.
  • SFXCL enhancement:
  • /TransferType flag: Specify the transfer type for all the files in an operation.

New in SecureFX 6.7.0 Build 110 Beta (Mar 9, 2011)

  • New features:
  • Added the ability to set and open bookmarks for frequently used folders.
  • Added an optional connect bar, which allows a connection to be made by entering the host on the toolbar.
  • Added an option to the Connect dialog to sort sessions logically, which is helpful when session names contain numbers.
  • Added the ability to copy and paste files from Eclipse to SecureFX.
  • SFXCL: Added a flag "/TransferType" which specifies the transfer type for all the files in the operation.
  • SFXCL: Added the ability to specify that the log file should be overwritten.
  • Changes:
  • If the option "Verify status on retrieve" is set, a STAT will always be issued before getting a file. This makes the progress information more accurate for multiple file transfers if a file size changed between the time the transfer was started and the file was transferred.
  • SecureFX and SFXCL logs now indicate whether a file was transferred as binary or ASCII.
  • A duplicate message that was logged for file transfers statistics in server-to-server transfers was removed.
  • Entering the license data now registers the application for all users instead of only for the current user.
  • FTP: Changed the default value of the global options "Send Size" and "Receive Size" to 65535 in order to improve FTP transfer speed.
  • FTP, FTP/SSL: SecureFX attempts to use the control address for data connections first, which speeds up connection time in most cases. This change is only seen in new sessions.
  • FTP/SSL: When attempting to connect, a message showing the remote host is now logged.
  • SFXCL: Output is now written to stdout instead of stderr.
  • Bug fixes:
  • SecureFX crashed if a session was reconnected after its protocol was changed from FTP to SFTP.
  • SecureFX could crash when a second instance was started.
  • If the maximum number of parallel transfers was set to 8, SecureFX became unresponsive when attempting to transfer a large number of files (e.g., 10,000).
  • SecureFX was unable to download files from an EldoS server.
  • If the option "Disable directory tree detection" was set, file attributes were not set during transfer operations.
  • Double-clicking a folder that the current user did not have access to left focus in that folder.
  • SFXCL: If the "noprompt" parameter was specified, the invalid public key error was not reported.

New in SecureFX 6.6.2 Build 350 (Feb 3, 2011)

  • Changes:
  • When Windows Explorer file types exist, they are used for displaying file icons in the local window and for opening files with the correct application.
  • Bug fixes:
  • SecureFX could crash if a synchronization operation was run and files had changed.
  • If a file was transferred using the transfer queue and then "Transfer Selected" was attempted on the file in the transfer queue, SecureFX crashed.
  • An IPv6 address could not be entered as a hostname for a session.
  • URL syntax was not being honored for the hostname in the Quick Connect dialog.
  • SFXCL: If a server-to-server transfer was specified using the /S syntax for the source and destination and the file did not exist on the source, SFXCL hung.
  • SFXCL: When incorrect syntax was specified on the command line, SFXCL incorrectly returned 0.
  • SFXCL: In a multi-file transfer, if some files transferred successfully, but others did not, SFXCL incorrectly returned 0.

New in SecureFX 6.6.1 Build 289 (Nov 5, 2010)

  • Bug fixes
  • If the file being transferred already existed on the destination and rename was selected in the replace prompt, the specified rename file was not on the destination
  • The session .INI-file-only option "Disable MLSX" was not being honored when it was on
  • The icons on the Window menu for tabbed groups were not correct

New in SecureFX 6.6.0 Build 278 (Oct 22, 2010)

  • During synchronize operations, transfer operation output is now sent to the log file in addition to the synchronize view's log window.

New in SecureFX 6.6.0 Build 257 Beta 5 (Oct 1, 2010)

  • Bug fixes:
  • Resuming an interrupted folder transfer could put files in the wrong folder.
  • When SecureCRT was also installed, if the Global Options dialog was closed when the Terminal/Advanced category was active and the Global Options dialog was restarted, the active category was File Transfer/Options/Advanced.
  • If the transfer queue was enabled, the View menu showed that the transfer queue was disabled when a remote file was being edited.
  • SCP: If a file was edited remotely and saved, SecureFX crashed when attempting to upload it.
  • SFTP: If a file was edited remotely, when the file was saved and uploaded, the remote file did not have the correct timestamp.
  • SFTP: Duplicate messages were logged when transferring files.
  • The following changes were made to log file output:
  • Status text for upload and download transfers changed from "Remote file closed." to "Source file closed." or "Destination file closed."
  • "Failed to close remote file." became "Failed to close destination file." or "Failed to close source file."

New in SecureFX 6.6.0 Build 247 Beta 4 (Sep 17, 2010)

  • Changes:
  • The following changes were made to log file output: - All server-to-server "Skipping file transfer" messages are now tagged with "" rather than "".
  • "Source path '' does not exist.\n\nIt will be skipped." became "Failed to retrieve information on the source item (). It will be skipped."
  • "Failed to retrieve information on the source item. It will be skipped." became "Failed to retrieve information on the source item (). It will be skipped."
  • "Checking remote directory status..." became "Checking destination directory status..."
  • "Reading remote site directory..." became "Reading source directory..."
  • "Reading local directory..." became "Reading source directory..."
  • Bug fixes:
  • SecureFX could crash during a "mirror both" synchronization operation if more than one directory at a time was being synchronized.
  • When connecting to an MVS server that sent characters other than decimal digits for the "Used" field, files could not be listed or downloaded.
  • Uploading failed when directory tree detection was disabled.
  • When multiple folders were transferred in parallel, if one of the transfers was cancelled, the next transfer started, but so did the previously cancelled transfer, which could no longer be cancelled.
  • When multiple files were transferred in parallel, if a file of unknown type was transferred and ASCII was specified to apply to all files of unknown type, it was only honored for the one file.
  • When an item in the transfer queue failed to transfer, it could prevent the queue from processing other items.
  • The "Choose Transfer Type" dialog was displayed multiple times for files with the same extension after specifying the transfer type to be used for all files.
  • When folders were transferred in parallel, if a file collision occurred, the overwrite prompt was displayed twice.

New in SecureFX 6.6.0 Build 232 Beta 3 (Sep 17, 2010)

  • Bug fixes:
  • When folders were transferred, a single file was transferred at a time regardless of the "Maximum number of parallel transfers" value.
  • If an attempt was made to create a new folder in a location where access was denied, SecureFX crashed.

New in SecureFX 6.6.0 Build 222 Beta 2 (Aug 18, 2010)

  • Changes:
  • SSH2 / SFTP / SCP: Socket write errors are now written to trace output.
  • Bug fixes:
  • SecureFX could crash when a synchronize operation caused files to be deleted on the local machine.
  • When files were being transferred in parallel, cancelling out of the Choose Transfer Type dialog caused the remaining files to get stuck at "Checking destination" and they could not be cancelled.
  • During synchronization, when the direction was Download, the local path was not displayed.
  • The color depth of some of the icons on the toolbar was reduced, which caused them to look pixelated.
  • SFXCL: When multiple files were transferred and a file transfer failed, the log reported that all files were transferred successfully.

New in SecureFX 6.5.4 Build 555 (Aug 11, 2010)

  • Bug fixes:
  • SecureFX could crash when a folder with many subfolders was traversed using the arrow keys.
  • Recursive transfers failed when the hierarchy was disabled (e.g., when the "Disable directory tree detection" option was set).
  • If a file transfer was interrupted and then later resumed to completion, a failure code was reported.

New in SecureFX 6.6.0 Build 206 Beta 1 (Aug 4, 2010)

  • New features:
  • Limit or "throttle" the bandwidth used during file transfers to keep from consuming all available bandwidth.
  • Specify the number of parallel file transfers and, as transfers are completed, queued files will continually fill available slots.
  • Selecting Download on remote files automatically places the files in the local CWD if a different download location has not been specified.
  • If a PASV data connection fails, SecureFX automatically tries to reconnect using the original host/IP address.
  • Added an Upload button that can be used for menu and toolbar customization.
  • The same file size display options that were previously available for the transfer window are now also available for the tree view.
  • SSL: Support for RFC 2228 Clear Command Channel (CCC) provides enhanced compatibility with SSL servers.
  • FTP/SSL: Available and negotiated SSL algorithms for implicit as well as explicit connections are now logged.
  • SFTP: Added the session INI-file-only option "Preferred SFTP Version" that forces SecureFX to use a specific SFTP version.
  • SSH2: Added support for the "null" host-key algorithm for GSS-KEX as specified in RFC 4462.
  • SFXCL: A password can be specified when using a session with SFXCL.
  • SFXCL: Added two new options to the /S switch. The "TransferType" option allows the transfer type to be specified independently of the file type. The "Attr" option allows the file type to be specified independently of the transfer type.
  • Changes:
  • When the "Trace Level" is set to 9, the password is automatically redacted from the trace output.
  • Bug fixes:
  • SecureFX could crash if a file was being edited or transferred and the remote connection was lost.
  • SecureFX crashed or hung if the transfer queue refreshed while renaming a previously transferred file.
  • If a saved synchronize session that used a session with no file transfer protocol specified was run, SecureFX crashed.
  • Files could not be uploaded to a directory that had write access, but not read access.
  • SecureFX failed to transfer multiple items in the transfer queue when the connection count was limited.
  • When a file was dragged into the queue, the file was not always transferred to the current working directory.
  • Direct server-to-server transfers did not update the time remaining and the throughput correctly.
  • If the last location in the local window was My Computer or My Network Places (Network Neighborhood), it was not restored when SecureFX was restarted.
  • Quick Connect sessions where the host was an IPv6 address could not be saved.
  • If a previously failed item in the transfer queue was re-queued in order to wait for a connection to become available, it could potentially get re-queued over and over and display a large number of failed transfer dialogs.
  • On Windows, when large font (120 DPI) was used, text on some dialogs was truncated.
  • FTP: If a file was downloaded to a local mapped drive, SecureFX reported that 0 bytes were downloaded, even though the file was not empty.
  • SFTP: When connection failed, socket-level errors were not reported or logged.
  • SFTP: Server-to-server transfers did not log all output for SFTP connections.
  • SFXCL: When attempting to authenticate using keyboard-interactive authentication and the password was specified in a URL or a session, there was a password prompt.

New in SecureFX 6.5.3 Build 490 (May 12, 2010)

  • Bug fixes:
  • When SecureFX was integrated with SecureCRT, if a session had a Terminal protocol specified and then a File Transfer protocol was specified, the terminal port was used as the default file transfer port.
  • The ClearType Windows system setting was not being honored.
  • SFXCL: SCP file transfers using URL syntax failed.

New in SecureFX 6.5.2 Build 446 (Mar 11, 2010)

  • Changes:
  • The SecureFX version in the Windows uninstall "DisplayVersion" registry key now contains the point release number in addition to the major and minor version numbers.
  • Bug fixes:
  • SecureFX crashed after selecting the right-click menu item"Go To->Home/Root" on a remote session that could not connect.
  • Cancelling out of the Choose Transfer Type dialog caused all transfers to go into the pending state rather than cancelling all the transfers as it did in prior versions.
  • FTP/SSL: Unencrypted data connections failed when using PORT.

New in SecureFX 6.5.1 Build 410 (Jan 22, 2010)

  • Changes:
  • Under Windows 7 and Vista, removed the prompt for making SecureCRT
  • the default Telnet application since many applications, such as
  • Internet Explorer 8, do not allow Telnet.
  • Bug fixes:
  • If SecureCRT was in the process of closing and the close button
  • was pressed again, SecureCRT could crash.
  • SecureCRT could crash when printing to an Adobe PDF printer using
  • pass-through printing.
  • If the global options "Use trackable insertion caret" was set, the
  • cursor did not blink.
  • If SecureCRT and SecureFX were integrated and the terminal or
  • file transfer protocol was changed to "None", the change was not
  • saved.
  • In the Key Generation wizard, if a key was generated and then the
  • user clicked "Back", changed the size of the key, and answered
  • "Yes" to the prompt about regenerating the key, the key was not
  • regenerated.
  • The menu was not expanded when the ALT+ key was pressed.
  • If a line of text that contained an end-of-line character was
  • copied and pasted, the end-of-line character was not included.
  • If a URL contained international characters and the URL was opened
  • using "Open URL" or CTRL+, the URL was cut off before
  • the first international character.
  • On Windows 7 and Vista, if a previous version of SecureCRT was
  • running prior to installation and the installation option
  • "Automatically close and attempt to restart applications" was
  • selected, the previous instance of SecureCRT was not closed and
  • could only be closed from the task manager.
  • On Windows 7 and Vista with Aero enabled, if a custom menu was
  • used, the Close button on the main SecureCRT window appeared to
  • be disabled even though it was not.
  • Serial: Disconnecting and reconnecting the physical RJ45 cable
  • connector caused SecureCRT to crash.

New in SecureFX 6.5.0 Build 400 (Jan 22, 2010)

  • Bug fixes:
  • SecureCRT could crash if the application's Close button was pressed more than once.
  • If a key was mapped to a string that contained "p" (pause), SecureCRT crashed when the key was pressed in the terminal window.

New in SecureFX 6.5.0 Build 371 Beta 5 (Dec 3, 2009)

  • Bug fixes:
  • If a .XML custom menu and toolbar file contained a menu on the toolbar, SecureFX crashed when trying to import it into version 6.5.
  • On Windows 7, if the Global.ini option "Disable Aero Peek" was enabled and an Auto session was specified, SecureFX crashed on start up.

New in SecureFX 6.5.0 Build 358 Beta 4 (Nov 11, 2009)

  • Changes:
  • When a session connects to VShell 2.5.0, it automatically falls ack to SFTP version 4 because, even though VShell 2.5.0 tries to negotiate SFTP version 5 or 6, it does not support those SFTP versions.
  • Added a Global.ini-file-only option to disable the Windows 7 Aero task bar peek functionality.
  • Bug fixes:
  • SFXCL: SFXCL could crash when using /Synchronize to do an upload-only synchronize if it needed to stat a remote file during an upload.

New in SecureFX 6.5.0 Build 335 Beta 2 (Oct 16, 2009)

  • Changes:
  • SSH2: When an RSA key is used for authentication, only the private key is required, which makes it easier to use Amazon EC2 keys.
  • Bug fixes:
  • If SecureFX was minimized, the live preview in the Windows 7 taskbar displayed a busy circle until it eventually failed to get a thumbnail bitmap and displayed a default icon.
  • If the tab display was off, the live preview thumbnail in the Windows 7 taskbar did not display the obscured area of the sessions that overlapped or were outside the main window.

New in SecureFX 6.5.0 Build 324 Beta 1 (Oct 2, 2009)

  • New features:
  • SecureFX has a tabbed interface option that puts the local window
  • and remote sessions into tabbed groups. Grouping options include
  • two vertically split groups, two horizontally split groups, and a
  • single group.
  • Added support for SCP as a file transfer protocol. It can be
  • found in the list of file transfer protocols in the Session
  • Options dialog and can also be specified in SFXCL.
  • To make it easier to navigate to the parent folder, ".." is
  • displayed in the local and remote sessions.
  • A command-line option /SESSION_FOLDER allows all the sessions
  • in a folder to be connected when SecureFX starts.
  • In the Open With dialog, an option was added to permanently
  • associate an application with a file extension within SecureFX.
  • FTP/SSL: Added the FTP/SSL session option “Use unencrypted data
  • channel”.
  • SFXCL: Added a parameter, /Command, that sends an FTP command prior
  • to connecting.
  • SFXCL: Added an option to specify that a QuickSync operation should
  • not include subdirectories.
  • Changes:
  • The transfer queue automatically scrolls to show the currently
  • active transfer.
  • The session Operating System setting is used to determine how
  • to translate the line ending characters for ASCII transfers.
  • The file transfer queue uses the date and time format from the
  • regional settings in Windows.
  • Bug fixes:
  • SecureFX crashed if a file in the file view pane was being renamed
  • and then the Refresh button on the toolbar was pressed.
  • If a transfer was interrupted and the destination file size was
  • equal to or greater than the source file size, SecureFX would hang.
  • If a session was in the middle of a large download and the server
  • disconnected, SecureFX did not attempt to reconnect and retry the
  • download.
  • If the current folder was deleted outside of SecureFX, it was no
  • longer possible to navigate folders in SecureFX.
  • If a session without a username was edited while it was connected,
  • the username entered during authentication was saved to the
  • session.
  • If the configuration folder's path had a trailing backslash,
  • sessions could not be connected from the Activator or from
  • SecureCRT (if it was installed).
  • The transfer queue status did not update when a queued transfer
  • was cancelled.
  • If the installer was run in silent mode and an answer file that
  • could not be found was specified on the command line, a dialog
  • was displayed.
  • FTP: SecureFX crashed if an empty quote command was specified.
  • SSH2: If the remote server supported substitute user, after a file
  • was downloaded, the "Substitute User..." menu item was disabled.
  • SSH2: In the Key Generation wizard, if the specified path for the
  • key contained two or more folders that did not exist, the key
  • could not be saved.

New in SecureFX 6.2.2 Build 263 (Jul 2, 2009)

  • Changes:
  • Added support for administratively prohibiting checking for updates from within SecureFX
  • Bug fixes:
  • SecureFX crashed when an attempt to transfer a file from Internet Explorer was made
  • SecureFX crashed if an attempt was made to use a session that had been disconnected by an internal timeout
  • SecureFX crashed if "/../.." was entered in the address bar, the root folder ("/") was selected, and then "/../.." was entered in the address bar again
  • SecureFX could crash if a session was in the middle of reconnecting when an attempt to navigate to a different folder was cancelled
  • Entering a path in the address bar could occasionally cause
  • SecureFX to display duplicate entries and crash
  • The installer did not honor LICENSE_FILE or CONFIG_FOLDER_PATH entries that were specified in an ANSWERFILE
  • Silent installs did not add the program to the Start menu or the list of installed programs in the Windows Control Panel
  • SSH2: Previously, the default GEX preferred key size was changed from 2046 to 2048. However, the GSSAPI GEX maximum key size was still 2046, which caused the server to report an error and disconnect the session when GSSAPI GEX was used.

New in SecureFX 6.2.1 Build 115 (Apr 29, 2009)

  • Bug fixes:
  • SecureFX could not be installed on systems where InstallShield
  • custom actions do not work.
  • If a license with a maintenance date in the format MM-DD-YY was
  • entered, SecureFX crashed.
  • In the Synchronize dialog, if the "Download only" or "Mirror
  • remote" option was selected, the local and remote paths were
  • switched in the dialog. The synchronization operation used the
  • correct paths.
  • In the Connect dialog, a session that was copied could not be
  • pasted more than two times.
  • If the Visual Studio 2008 DLLs were not in the side-by-side
  • cache, MFC90.DLL errors were written to the event viewer when
  • SecureFX ran.
  • FTP: File attributes were not shown for FTP servers that used
  • UNIX.* file attributes, such as NcFTPd Server.
  • FTP: If the default transfer type was set to ASCII, SecureFX
  • issued a SIZE command after a LIST of the file, which caused
  • some servers to report the error "Failed to retrieve information
  • on the source item. It will be skipped."
  • SFTP: SecureFX could crash while attempting to transfer a file
  • from a security gateway, such as the GENBAND S2(TM) Security
  • Gateway.
  • SSH2: If an RSA key with a passphrase was added in the Manage
  • Agent Keys dialog and the wrong passphrase was entered, the
  • incorrect error "The key packet is corrupt, damaged, or
  • incompatibly formatted" was reported and was still reported
  • after the correct passphrase was entered.

New in SecureFX 6.2.0 Build 183 Beta 3 (Mar 19, 2009)

  • SecureFX crashed if the File menu was selected after the menu
  • bar was reset to Default from the Menus tab in the Customize
  • menu.
  • When generating a public key in the Key Generation wizard, the
  • progress bar was not displayed until after the key had been
  • generated.
  • Three-year licenses were not being honored.
  • In the Connect dialog, when a new folder was added, a folder
  • called "New Folder" was also added.
  • In the Connect dialog, attempting to rename a session to the same
  • name as its parent folder reported an error that the name was
  • already in use.
  • After pasting a copied session into a folder in the Connect
  • dialog, the folder was selected.
  • SSH2: Attempting to authenticate using GSSAPI with the 64-bit
  • MIT Kerberos DLL failed.

New in SecureFX 6.1.4 Build 489 (Feb 24, 2009)

  • Bug fixes:
  • SFXCL: Attempting to rename a file using /RENAME resulted in a syntax error if the second letter in the file was "s".

New in SecureFX 6.2.0 Build 162 Beta 2 (Feb 18, 2009)

  • Bug fixes:
  • On a 64-bit machine, Help could not be launched.
  • In the Connect dialog, if several sessions were selected and one
  • was de-selected, when the mouse was right-clicked to display the
  • context menu, the session was selected.
  • If the login failed when attempting to connect to an FTP/SSL
  • server, the "Login Failed" message appeared after the correct
  • password was entered.
  • For synchronize operations, the "Include subdirectories" option
  • was not being honored.
  • The 64-bit combined SecureCRT and SecureFX installer installed
  • into the x86 location when run in silent mode.
  • In the installer, on the dialog that shows where the
  • application is going to be installed, long install location
  • paths were cut off.
  • The upgrade eligibility date displayed in the installer was not
  • correct.

New in SecureFX 6.2.0 Build 147 Beta 1 (Jan 30, 2009)

  • New features:
  • A native 64-bit Windows version is available.
  • Added filter support to Quick Synchronize and Synchronize
  • operations. The new functionality supports wildcards and allows
  • files and folders to be included or excluded.
  • Multiple sessions can be selected and edited from the Connect
  • dialog. Only the changed fields will be applied to the
  • selected sessions, which allows specific settings to be
  • changed for a group of sessions.
  • There is a new option to remember which sessions were open the
  • last time SecureCRT ran so that they can be launched the next
  • time the application runs.
  • FTP, FTP/SSL: Added the ability to specify a range of ports for
  • SecureFX to use when making an FTP or FTP/SSL data connection.
  • FTP/SSL: Added support for generating and using self-signed
  • certificates, which allows mutual authentication.
  • SSH2: Added support for PKCS#11, allowing a Cryptographic Token
  • Interface to be used for smart-card authentication.
  • SSH2: In the Activator, agent support has been enhanced by
  • allowing keys to be explicitly added and removed.
  • Changes:
  • SFXCL: If a password is specified on the command line, it is not
  • written to the log file.
  • SSH2: Added support for specifying a password in the Session
  • Options dialog.
  • SSH2: The default public key generation folder has been changed
  • to "My Documents". Only new installations are affected.
  • SSH1/SSH2: When creating an identity file, moving the mouse is
  • no longer required to generate random data.
  • FTP/SSL: Modified the error message reported when SSL-certificate
  • negotiation fails to give more information about what the problem
  • might be.
  • Bug fixes:
  • When the screen reading software JAWS 8 was running, SecureFX
  • could crash or report an "out of memory" error.
  • When using the transfer queue, if multiple files were uploaded to
  • a server that used a SecurID token, the password had to be entered
  • for each file.
  • In the Global Options dialog, changes to options were saved when
  • the dialog was cancelled.
  • When the remote server was PureFTPd, the file permissions
  • attributes value shown in the Properties dialog was "0" even
  • though the log showed a non-zero value.
  • If a firewall was specified on the command line and the firewall
  • name contained a space, it was not used.
  • SFXCL: Under certain circumstances, if a public key or passphrase
  • was specified on the command line, SFXCL crashed.
  • SFXCL: Under certain circumstances, transferring files to MVS
  • servers did not work even though they worked in SecureFX.
  • SFXCL: If a firewall was specified using the /FIREWALL parameter,
  • it was not used.

New in SecureFX 6.1.3 Build 423 (Dec 3, 2008)

  • SSH2: The default cipher list has been modified to prefer the AES
  • ciphers in CTR mode. This change was made to address a potential
  • vulnerability. See the following web page for more information.

New in SecureFX 6.1.2 Build 409 (Nov 7, 2008)

  • SecureFX crashed after connecting to a session if SecureFX was unable to bind the port sent by the server.
  • If the system color quality was changed to 16 bit, SecureFX's address bar text became bold.
  • SFTP: Under certain circumstances, if a refresh was done on a connection that had disconnected, SecureFX crashed.

New in SecureFX 6.1.1 Build 383 (Oct 3, 2008)

  • SecureFX 6.1 could not connect to VShell versions 2.3.x through 2.4.3.
  • In the Connect dialog, doing a Find Next after deleting a session that had been found using Find caused SecureFX to crash.
  • In the Global Options dialog, on the Advanced category under File Transfer, an "Invalid Octal digit" message was displayed even though the values were valid.
  • Global Secure Shell configuration information was not being migrated.
  • If two sessions had the same name, hostname, and username, they were combined during migration, but only the terminal protocol was set.

New in SecureFX 6.1.0 Build 349 (Aug 22, 2008)

  • Under certain circumstances, SecureFX did not preserve the timestamp on an uploaded file.
  • When Windows was configured to use large fonts (120 DPI), some text in the Session Options dialog did not fit in the dialog.

New in SecureFX 6.1 Beta 4 (Jul 31, 2008)

  • Under certain circumstances, launching SecureFX caused MFC80U.dll errors to be reported in the Windows Event Viewer.

New in SecureFX 6.0.3.311 (Jul 25, 2008)

  • Under certain circumstances, files that should have been displayed sometimes were not displayed.
  • When the SecureFX window regained focus, sometimes it was not repainted.
  • The installer did not handle the answer file option INSTALLATION_PROFILE.

New in SecureFX 6.1 Beta 3 (Jul 18, 2008)

  • Under Windows 2000, a KERNEL32.dll error was reported when SecureFX started.
  • SecureFX crashed if a synchronize session's .INI file contained a blank line.
  • For files larger than 4GB, the Local window showed an incorrect file size.
  • File listings were not shown when connecting to a SurgeFTP server.
  • The Activator used a different configuration folder than SecureFX when SecureFX specified the /F command-line option.

New in SecureFX 6.1 Beta 2 (Jul 3, 2008)

  • Under Vista, when a new synchronize session was created, garbage was displayed in the "Last Synchronized" column in the Synchronize dialog
  • FTPS sessions incorrectly honored the "Directory listing options" when connecting to a server that supported MLSD
  • If SecureFX was running during an upgrade install, the installer continued to report that a file was in use after SecureFX was closed and Retry was selected
  • The installer did not handle the answer file option INSTALLATION_PROFILE

New in SecureFX 6.1 Beta 1 (Jun 20, 2008)

  • New features:
  • Added support for saving, editing, and executing synchronize
  • operations, which makes it easier to keep multiple sites
  • synchronized.
  • The Quick Synchronize and Synchronize dialogs optionally use the
  • paths from the active sessions for the synchronize operation,
  • reducing synchronize set up time.
  • Added folder operations which make it easier to navigate folders
  • in SecureFX. The new context menu items are: Back, Forward,
  • Parent, Home, Root, and Folder in Explorer (local session only).
  • Added the ability to search sessions and folders in the Connect
  • dialog, which supports searching for a session name, hostname,
  • folder name, or a keyword in the description.
  • SSH2: The username and password can be saved when using keyboard-
  • interactive authentication, streamlining the logon process.
  • SFTP: If the remote server is VShell 3.5 or later, there is a
  • context menu item that allows you to become a different user.
  • Bug fixes:
  • Under certain circumstances, when uploading multiple files through
  • the Transfer Queue, the transfer hung on the second file.
  • When the "Save expanded folder state in connect dialog" option was
  • set and a session in a folder was renamed in the Connect dialog,
  • it caused other folders to be expanded.
  • SFTP: If the contents of a folder could be viewed, but not listed,
  • SecureFX got an unknown application error when attempting to
  • change to the folder.
  • U3: Configuration settings were uninstalled when the U3 version
  • was uninstalled.

New in SecureFX 6.0.2 (Apr 25, 2008)

  • Changes:
  • Dot files, such as ".svn", that are in the configuration folder are no longer displayed in the Connect dialog.
  • Bug fixes:
  • If the SecureFX command line specified a configuration folder that did not contain a default session, it crashed on startup.
  • If SecureCRT and SecureFX were installed separately but used the same configuration folder, when a session was created or modified, the protocol for the other application was set to None.
  • Under certain circumstances, the installer incorrectly reported a "file in use" error, which prevented the application from being installed.
  • Under Vista, if an MSI installer was used, the default installation folder was in "Application Data" instead of "Program Files".
  • FTP: Folders were sometimes not displayed for some FTP servers,such as NcFTPd and Serv-U.
  • SFTP: When downloading files using multiple buffers, some servers did not honor SecureFX's buffer size request, which resulted in files not being transferred correctly.

New in SecureFX 6.0.1 (Feb 21, 2008)

  • When using a U3 smart drive, valid license data was not saved if the first attempt to enter the license had invalid data.
  • SSH2: When an attempt to upload a public key from the Quick
  • Connect dialog was made and the hostname had not been specified, SecureFX crashed.
  • SSH2: After changing the password on an OpenSSH 3.6 server,
  • SecureFX crashed when attempting to logon.

New in SecureFX 6.0.0.168 Beta 5 (Jan 9, 2008)

  • File browser dialogs could not be resized.
  • SSH2: When the path for the identity file contained anenvironment variable, the Public Key Properties dialog could not display the fingerprint, upload the key, or change the passphrase.
  • SSH2: In the Public Key Properties dialog, if the key file path was blank, it was filled in after cancelling out of the file browser.

New in SecureFX 6.0 Beta 4 (Dec 18, 2007)

  • SecureFX crashed if a remote session was closed while a file listing was in progress.
  • The recent session list wasn't updated when a session was selected from the Activator.
  • SFXCL: An incorrect error code was returned for the "No configuration is specified" error.

New in SecureFX 6.0.0.151 Beta 3 (Dec 7, 2007)

  • The installer no longer requires a reboot upon completion.
  • The U3 installer is now packaged as a .exe instead of a .u3p. This prevents it from being downloaded as a .zip.
  • Quick Connect did not work when the "Save session" check box was unchecked.
  • When a recently used session path was too long to fit in the menu, the path was truncated before the session name.

New in SecureFX 6.0.0.129 Beta 1 (Nov 16, 2007)

  • Added an address bar to the local and remote session windows that contains a history of folders that have been navigated to and allows a path to be entered manually.
  • Quick Synchronize now supports mirroring with delete, which makes the contents of the destination folder exactly the same as the source folder.
  • Enhanced portability by making a U3 installer available. Installing SecureFX on a U3 drive makes it easier to use on any machine.
  • Added MSI installer support.
  • Added support for several Windows themes, which give the user interface a more modern appearance.
  • Added support for customizing the toolbar and menu by dragging and dropping items while in the Customize dialog.
  • Added an option to resolve symbolic links automatically.
  • Environment variables can be used in all paths specified in global and session options, which allows configuration files to be used by more than one person and makes it easier to move configuration files to other machines.
  • Improved speed of local window file listings for folders that contain a large number of files.
  • The queue overwrite prompt now has "Yes to all" and "No to all" options.
  • If a transfer type is "Unknown", the default transfer type is used.
  • The standard toolbar icons have been updated to use Windows Vista icons.
  • SecureFX dialogs now use the font specified by the Windows display properties.
  • Added optional monthly pop-up dialog that offers to check for product updates.
  • Improved the error message that is displayed when attempting to give a session a name that is already being used.
  • Added a command-line flag "/S:i", which specifies that the session's initial directory should be used.
  • FTP/SSL: The list functions MLST/MLSD are used by default when they are supported by the server.
  • SFXCL: Added the /F command-line option to the usage message.
  • Fixed: On an MVS system, when uploading a file to a directory that contained a "." in the name, the path of the uploaded file was not correct.
  • Fixed: SFTP: If the connection was lost during an upload, the transfer continued, which caused the entire file to be loaded into memory.
  • Fixed: 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".
  • Fixed: SFXCL: A prompt was displayed in noprompt mode if the logon failed for an FTP or FTP/SSL session.

New in SecureFX 4.5.1 (May 18, 2007)

  • 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

New in SecureFX 3.1.2 (May 25, 2006)

  • SFTP: SecureFX no longer reports a confusing trace output message about an unexpected packet size because it was not an error.