VanDyke Software

SecureFX History

                SecureFX(R) 9.3 (Beta) -- June 28, 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 

Changes in SecureFX 9.3 (Beta 1) -- June 28, 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 and 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.


  - 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

  - 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

  - 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.