七麦数据

This version adds support for iOS 26 and the ability to duplicate saved sessions. It also addresses a crash when clicking into the terminal after connecting and bugs related to importing from an XML file.

We want your feedback. Please send your feature requests and bug reports to support@vandyke.com.

Changes in SecureCRT for iOS 4.0.1
----------------------------------

New Feature:

- Added the ability to specify the character encoding for a session.

Bug Fixes:

- iOS 26: If a text selection was adjusted via the selection drag handles, SecureCRT crashed.

- iOS 26: With certain color schemes, the keyboard accessory view was difficult to see.

This version adds support for iOS 26 and the ability to duplicate saved sessions. It also addresses a crash when clicking into the terminal after connecting and bugs related to importing from an XML file.

We want your feedback. Please send your feature requests and bug reports to support@vandyke.com.


Changes in SecureCRT for iOS 4.0
--------------------------------

Known Issue:

- SecureCRT crashes when a text selection is changed with the drag handles.

New Features:

- Added support for iOS 26.

- Added the ability to duplicate saved sessions.

Bug Fixes:

- SecureCRT could have crashed when clicking into the terminal after connecting.

- SecureCRT hung when launched after importing an XML file that included a local shell auto session.

- When moving a session or folder to a location that already contained a session or folder with the same name, the operation appeared to hang because the error reported was not displayed.

- Global options were not correctly imported from an XML file.

- If the on-screen keyboard was visible when the new host key dialog was shown, the accept host key buttons may have been cut off.

- iOS 26: When the SecureCRT window was resized and moved, the last line of the terminal view may have been cut off by the keyboard input accessory view.

- On an iPhone, when using OEM character encoding and connecting to an ANSI BBS server, the bottom rows of text might not have been displayed.

Changes in SecureCRT 3.0.1
--------------------------

Vulnerability Fix:

- SSH2: For some algorithms, an attacker can manipulate the packets sent during key exchange to cause some packets to be removed, which compromises channel integrity. A "Strict KEX" extension was implemented to address this vulnerability (CVE-2023-48795). In order to use the "Strict KEX" extension, the extension must be supported by both the client and the server.


Bug Fixes:

- On iOS 17, when a text selection was started in the terminal view, SecureCRT may have crashed.

- On iOS 17, if the backspace key was held down while focus was in the terminal, the key did not repeat.

- On iOS 16, when scrolling into the scrollback buffer in a session configured with a large font size, scrolling back down to the prompt may have failed.

- If the public key specified for a session contained a "." in the filename, an error that the private-key file could not be found was reported.

Changes in SecureCRT 2.5.2
--------------------------

Change:

- The keyboard function key view now includes the F11 and F12 keys.

Bug Fix:

- When scrolling through data in the scrollback, the view may have jumped to the very top or very bottom of the view.

Changes in SecureCRT 2.5.1
--------------------------

Bug Fixes:

- When importing a private key that was passphrase protected, SecureCRT could hang.

- In certain cases, importing a configuration archive file silently failed.

Changes in SecureCRT 2.5
------------------------

Vulnerability addressed:

- An external report claims that when using a brute-force attack, sensitive data, such as passwords, stored in the SecureCRT 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.

Bug Fixes:

- When attempting to download a file with Y/Zmodem, SecureCRT could have crashed.

- If a configuration was imported that included a hostkey database path that was not located under the main configuration directory, then hostkey acceptance may have failed immediately after the import. Restarting SecureCRT automatically fixed the problem.

- If a session that had zlib compression configured was imported, the compression could have unexpectedly changed to zlib@openssh.com.

- When the Session Options page was displayed and the device was rotated between landscape and portrait orientation, some of the option fields may have been cut off.

- When authenticating with an RSA public key, if agent forwarding was used to connect to another host, the SSH agent may have reported an "incorrect signature type" error.

- On iOS 16, the keyboard displayed a large blank space below the accessory view and the accessory view itself could have disappeared after the keyboard was hidden and restored.

Changes in SecureCRT 2.4.4
--------------------------

Bug Fixes:

- On iOS 16, SecureCRT crashed on startup.

- When copying a line that had wrapped in the view, newlines were inserted into the copied string at the point where the line wrapped.

Changes in SecureCRT 2.4.3
--------------------------

Bug Fixes:

- When using a mouse pointer (or potentially other pointer devices) within the terminal view, SecureCRT crashed.

- If the session Firewall page was displayed while the session had an invalid name specified, SecureCRT could crash.

- When prompted to import a configuration file that was placed on the device, SecureCRT could hang.

- On certain devices, when connecting to a session that did not have a hostname specified, SecureCRT could hang.

- On certain devices, when importing a private key, SecureCRT could hang.

- On certain devices, when creating a public key with a name of an existing key, SecureCRT could hang.

- On certain devices, if an email client has not been setup and the "Email Public Key" option is selected, SecureCRT could hang.

- On certain devices, when attempting to create a firewall with an invalid name, SecureCRT could hang.

- When the Session Options page was displayed and the device was rotated between landscape and portrait orientation, some of the option fields may have been cut off.

- When multiple sessions were connected and the visible session was closed due to the "Close on Disconnect" option being enabled, the text in the remaining session's view may have been hidden.

- On certain devices, when importing a private key, the passphrase field may have been obscured by a "Strong Password" label.

Changes in SecureCRT 2.4.2
--------------------------

Bug Fixes:

- On certain devices (e.g., iPhone 13 Pro), SecureCRT could hang at startup.

- On certain devices, when the "Confirm Disconnect" prompt was displayed, SecureCRT could hang.

- On certain devices, when attempting to save a session with an invalid name, SecureCRT could hang.

- When an error dialog was displayed from the configuration passphrase interface, SecureCRT could hang.

- When generating or importing a public key and the specified passphrases did not match, SecureCRT could hang.

- If the Session Firewall page was displayed while the session had an invalid name specified, SecureCRT could crash.

Changes in SecureCRT for iOS 2.4.1
----------------------------------

Bug Fix:

- On iOS 15, SecureCRT crashed when attempting to make a connection.