11/11/2022 0 Comments Securecrt full screen![]() ![]() 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 When a script enabled file logging for a connection, the "Timestamp each line" logging option may have inadvertently been enabled #Securecrt full screen windowsWindows: SecureCRT 9.1.1 is compatible with Windows 11 Change log not available for this version 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 When RDP or Local Shell sessions were exported and later imported to a different configuration, the protocol-specific options may not have been preserved as expected When connecting to a server that uses an X.509 certificate for the host key, even though the certificate met all requirements for automatic acceptance of the host key by the client, the application still prompted the user to manually accept and save the key If the Button Manager dialog was launched from the Button Bar Manager dialog, changes to the buttons were not saved 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 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 the "Make SecureCRT the Default Application" button was pressed, SecureCRT was not set as the default application for SSH or Telnet URLs 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 ![]() 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 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 When editing multiple sessions at once, the port field could not be changed ![]() 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 If a saved credential was modified while editing multiple sessions simultaneously, SecureCRT could have crashed ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |