However, when the TFTP server was running, SecureCRT was vulnerable to a directory traversal attack that allowed access to arbitrary files on the local system. TFTP: The TFTP server is off by default. 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. Added an optional "hide output" parameter to the Session Object Lock() method SecureCRT now handles the Xterm "paste bracketing" escape sequence so that indentation is correct when indented text is pasted into an editor The performance of keyword highlighting has been improved to be as fast as and in many cases, much faster, than version 8.5. Windows: Added an administrative policy that disallows the TFTP Windows: On the public-key authentication failed dialog, when the left and right arrows were used to change focus between the Skip and OK buttons, the focus moved the opposite direction of the arrow key pressed. Windows: If the Session Manager and Command Manager were docked within the same pane and configured to be auto-hidden, the expanded size of the managers could change when SecureCRT restarted If a script was launched from a button bar button or keymap shortcut and the script file could not be located, a misleading error was reported Mac/Linux: Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected or copied Windows: If the Session Manager and Command Manager were docked in stacked layout, the size of the individual manager windows was not retained between instances of SecureCRT Windows: When the Command Window was displayed, the height of the window increased by one pixel each time SecureCRT was restarted 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, if the CAPI store contained multiple certificates, there could have been a delay before being prompted for the smart card pin The display of certain Unicode characters (e.g., emojis) in the terminal could have caused other characters to appear as clipped When the sample ANSI color palette was shown for a color scheme, the colors displayed did not match the descriptive text for the color (e.g., "ANSI Red" text was displayed using the green color) Windows: If a user was denied remote desktop access on the target system, connecting with an RDP session silently failed without reporting the system error The script did run after the dialog was dismissed When a script was specified on the SecureCRT command line, the error "script is currently running" was incorrectly reported. Windows: When a disconnected RDP session tab was reused by a new RDP connection, the title bar text was not updated When performing a "Find" operation in the terminal view, if the end of the buffer was reached, the search direction could not be reversed If a script that made a connection was specified on the command line, a "script is currently running" error was incorrectly reported. Restored the ability to use the SHA1-96 and MD5-96 MACs 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 Windows: Under certain environments, when connecting to an RDP session, the remote display would not scale to match the local desktop 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 circumstances, when opening the Session Manager, some folders may not have been expandable 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 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: The Scratchpad and Script Editor now honor the "Use ClearType to smooth edges of screen fonts" global option Change log not available for this version When a script enabled file logging for a connection, the "Timestamp each line" logging option may have inadvertently been enabled Windows: SecureCRT 9.1.1 is compatible with Windows 11
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |