VanDyke SecureCRT and SecureFX 9.2.2.2794 + Portable + MacOSX

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.

- If multiple sessions were connected in tab groups, zooming the
font in one tab group could have caused the font zoom to be reset
in another tab group.

- Windows: If multiple RDP sessions were connected and the "Close
on disconnect" session option was enabled, closing the main window
could have resulted in a crash on exit.

- Windows: When the "Make SecureCRT the Default Application" button
was pressed, SecureCRT was not set as the default application for
SSH or Telnet URLs.

- Windows: When the confirm disconnect option was enabled and an
RDP session was connected, closing the application resulted in
multiple confirm disconnect prompts.

- 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 SecureCRT crashed and the user chose to report the crash,
the email template used for the report may not have contained
the correct version of SecureCRT.

- Mac/Linux: If the main window was closed while in full-screen
mode with a session connected, the next time that session was
opened, the window did not return to full screen mode.

https://www.upload.ee/files/14114772/VanDyke.zip.html

Change:

- Windows: The Scratchpad and Script Editor now honor the "Use
ClearType to smooth edges of screen fonts" global option.

Bug Fixes:

- When connected to a host using TN3270 emulation, if the current
partition was unformatted, the SETBUFFERADDRESS command was
unexpectedly included in SecureCRT's response.

- Windows: If a session was configured to use a firewall that
prompted for credentials, and that session was configured to
automatically connect at application startup, SecureCRT crashed.

- Windows: Under certain circumstances, when opening the Session
Manager, some folders may not have been expandable.

- Windows: When authenticating with a PKCS#11 certificate with
certain signature algorithms, the key may not have been added
to the SSH agent.

- Windows: Under certain environments, when connecting to an RDP
session, the remote display would not scale to match the local
desktop.

- Mac/Linux: If a log file was initially created with the "Append
to file" logging option enabled, Unicode characters may not have
been logged correctly.

Change:

- Restored the ability to use the SHA1-96 and MD5-96 MACs.


Bug Fixes:

- If a script that made a connection was specified on the command
line, a "script is currently running" error was incorrectly
reported. The script did run after the dialog was dismissed.

- When performing a "Find" operation in the terminal view, if the
end of the buffer was reached, the search direction could not be
reversed.

- Windows: When a disconnected RDP session tab was reused by a new
RDP connection, the title bar text was not updated.

- Mac/Linux: If the Session Manager was docked and not auto-hidden,
sessions could have appeared as duplicated when SecureCRT was
launched.

- Mac/Linux: Under certain scenarios, opening a tab in a new tab
group caused the terminal view to be blank.