SecureFX(R) 9.2.2 (Official) -- June 16, 2022
Copyright (C) 1995-2022 VanDyke Software, Inc.
All rights reserved.
This file contains the SecureFX product history. It includes lists of
new features, changes, and bug fixes sorted by release. For a product
description, installation notes, registration information, and contact
information, please refer to SecureFX_README.txt (downloaded with this
installation).
Changes in SecureFX 9.2.2 (Official) -- June 16, 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 to
enter 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.
Changes in SecureFX 9.2.1 (Official) -- May 12, 2022
----------------------------------------------------
Bug Fix:
- Windows: In certain cases, when moving focus from the hostname
field to the port field using the tab key, the text contained
within the port field was not selected.
Changes in SecureFX 9.2 (Official) -- April 26, 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.
Changes in SecureFX 9.2 (Beta 5) -- April 19, 2022
--------------------------------------------------
Changes:
- In the About box and other dialogs that contain hyperlinks, it is
now possible to tab to the hyperlink, which allows the links to be
read by screen reader software.
- When the Quick Connect dialog box is opened, focus is placed in
the Protocol dropdown list. This change was made for Section 508
(accessibility) compliance on Windows.
- Windows: The hint that is displayed in the Connect bar and Session
Manager filter bar remains visible until the user starts typing.
- Mac: The About box shows the architecture type (x64 or ARM64) of
the application.
Bug Fixes:
- Under rare circumstances, when downloading a file that would
overwrite an existing local file, the "Confirm Overwrite" dialog
displayed did not always include the "Resume" or "Rename..."
buttons.
- Mac: When connecting a session in which the configured firewall
was not found, the "Firewall not found" warning message could
get into a state where it could not be closed, causing the SecureFX
window to become unusable.
Changes in SecureFX 9.2 (Beta 4) -- March 31, 2022
--------------------------------------------------
Bug Fixes:
- If a file transfer was canceled while a remote directory listing
was in progress, SecureFX could have crashed.
- When remote editing a file with certain editors, a file lock could
have prevented the editor from writing changes to the file,
resulting in a zero byte file being uploaded to the remote system.
- When there were a large number of folders in the Session Manager
or Command Manager, using the "Expand All Folders" or "Collapse
All Folders" options could have taken a long time to complete.
- When using the "Personal data folder" configuration option, the
reference to a saved credential used by a session was stored in
the common session configuration file.
- Windows: When connecting to a session, focus was not placed within
the remote session window's tree view, and furthermore, using the
tab key did not move focus to the tree view or list view.
- Mac/Linux: When using the Quick Connect dialog to connect to a
host, the username and credential settings were not preserved
between uses.
Changes in SecureFX 9.2 (Beta 3) -- March 3, 2022
-------------------------------------------------
New Feature:
- In the Session Options dialog, Quick Connect, and New Session
Wizard, if a string like "user@host:port" is entered as the
username, it is parsed and the values are placed in the
appropriate fields.
Change:
- When connecting to a session that uses saved credentials, if the
credentials are not valid, the dialog that prompts for the
credentials has an option to specify whether or not the saved
credentials should be updated.
Bug Fixes:
- When the "Use a separate transport for every connection" option
was enabled and parallel file transfers were allowed, transferring
a folder structure that contained subfolders did not establish a
separate transport for each file transferred in parallel.
- When connecting using the FTPS protocol with an encrypted data
channel to certain versions of the Pure-FTPd server, the initial
directory listing may not have been displayed as expected.
- Under certain circumstances, file transfers started after a
disconnected session was reconnected may have stayed in a
"Pending" state.
- When an interrupted file transfer was resumed, the displayed
transfer progress percentage may have been incorrect when the
transfer completed.
- When using the "Personal data folder" option, changes made to an
option (e.g., username or password) stored in the personal
configuration caused the non-personal configuration file to be
written to disk.
- Windows: If the SFTP protocol was not installed, SecureFX could
have crashed when editing a saved credential.
- Mac: Under rare circumstances, certain text fields within the New
Session Wizard stopped accepting input.
Changes in SecureFX 9.2 (Beta 2) -- February 3, 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.
Changes in SecureFX 9.2 (Beta 1) -- January 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., Global\SSH2 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.
