Mac: When attempting to connect to a session using public key, if the remote host timed out and the connection was closed while the dialog prompting for the public key was displayed and then a public key file was chosen, SecureCRT crashed. Mac: On systems where the language and locale were set to something other than a North American language and locale, SecureCRT could crash when the Font button was pressed in the Terminal/Appearance category in the Session Options dialog.Windows: In some cases, the initial position of a session was different when the session was disconnected and then connected again.SSH2: It was not possible to specify the same port for port forwarding even if a different local IP address was used.Telnet, Raw: If an invalid port was entered in the New Session wizard and the Back button was pressed, SecureCRT crashed.Serial: SecureCRT could lock up if the session was disconnected during the Zmodem transfer.Serial: If a session was disconnected during a Zmodem upload, SecureCRT could crash.Selecting "Check for Updates" from the Help menu launched the VanDyke forums.The script function SendKeys() did not send text to the correct tab if the tab was switched while the script was running.In Python scripting, the failSilently parameter in the ConnectInTab function in the Session object was not implemented.The script function () always opened a new tab even when the "Reuse disconnected tabs" option was set.The session option "Keymap v3" could not be accessed from a script.No screen painting occurred while crt.Sleep() executed in a script.Attempting to save a recorded script to a location that was not writable failed silently, causing the script to be lost.After loading an invalid keymap, pressing CTRL+TAB to switch between tabs no longer worked.If a remote login banner contained a high-bit character, SecureCRT stopped displaying the banner when it hit that character.If a Quick Connect or local shell (Mac only) session was connected and closed and then the default color scheme was modified, a new Quick Connect or local shell session did not use the new color scheme.If two tabbed sessions were opened, but not connected, when the first tab was made active, its status indicator showed that it was connected.The session option to disable pass-through printing was not being honored.When a local port forward contained an IPv6 address, SecureCRT was not able to save the host key.When attempting to connect using a SOCKS proxy, if the SOCKS server replied fast during negotiation, it could cause messages to be received out of order, which caused the connection to fail.During initialization, if SecureCRT failed to acquire a Cryptographic Context, SecureCRT crashed when it closed.SecureCRT could crash if shortcut keys were used to select invalid operations in the Connect dialog.Under certain conditions, a race condition between terminating a script and closing SecureCRT could cause a crash.If the Xmodem sent packet size was set to 1024 bytes and a file that was 1024 bytes or larger was sent using Xmodem, SecureCRT could crash.If multiple instances of SecureCRT were running and they were all closed at the same time, the file containing the global settings could get corrupted, which caused SecureCRT to attempt migration the next time it ran.SSH2: Added support for reading AES-128 public keys.In deze release zijn de volgende veranderingen en verbeteringen doorgevoerd: Changes: Sinds versie 6.6.0 is er ook een versie van SecureCRT voor Mac OS X. Ssh is een methode om een beveiligde verbinding tussen twee computers op te zetten, waarbij zowel de data als een deel van het ip-verkeer wordt versleuteld. Iets minder simpel gesteld is het een client voor remote control, file transfers en datatunneling met behulp van ssh. SecureCRT is, simpel gezegd, een uitgebreide versie van Putty. VanDyke Software heeft versie 6.6.2 van SecureCRT uitgebracht.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |