Changes in SecureCRT 3.0.1 (Official Release) --------------------------------------------- Changes: - In the Connect dialog, F2 now initiates a rename on the selected item. - In the Connect dialog, when the user creates a series of new folders, but does not edit the names, new folder names are now numbered to have unique names (i.e. New Folder, New Folder (1) ). Bug Fixes: - In SSH1, eliminated "buffer overflow" error. - Attempting to run a non-existent .csf script would result in a GPF. - The order of items in the Connect dialog was incorrect after a drag and drop operation. - Copying and pasting a sub-tree of folders failed if the parent and child folders had the same name. - Session printer settings were ignored. - Changing the printer for a specific session would reset the global printer setting. - In the Connect dialog, when a copy of a session or folder was created and Auto Arrange was off, the copy was not inserted in alphabetical order. - When the Scrollback buffer option was set to 0 lines and a line was scrolled off the top, the new blank line at the bottom was not properly cleared. - Depending on the default printer selected, accessing the Printer page on both the Global and Session Options dialog could result in a GPF. Changes in SecureCRT 3.0 (Official Release) ------------------------------------------- Change: - In the Global Options dialog, the default value for line delay for pasting text and transferring files via ASCII send is now 5 ms (was 0 ms). - Added a second variant of the WaitForStrings() scripting function. Because of the way JScript and PerlScript pass arrays, the old function was only usable from VBscript. Bug Fixes: - Using SSH1, SecureCRT would occasionally try to close down the port forwarded channel twice. This resulted in SecureCRT displaying the error message, "Received double input eof". - SecureCRT would GPF when downloading a file via ZModem if the file had the date January 1, 1970. - In full screen mode, if the menu bar was turned off, the top line of the terminal window was hidden. Changes in SecureCRT 3.0 (beta 9) --------------------------------- New Features: - Added MENU_DISCONNECT function. - Added MENU_RECONNECT function. Bug Fixes: - In SSH2, an extra popup dialog could be displayed when a forwarded socket was closed. - The global preferences for SSH1 and SSH2 were both being stored in SSH2.ini in the config directory. Therefore, it was not possible to set a global private key file for both SSH1 and SSH2. - In SSH1, a change in 3.0 (beta 8) caused the /PASSWORD option to be ignored. - A change in 3.0 (beta 8) disabled the ability to edit session names in the Connect dialog. - Using Hold Screen (VT_HOLD_SCREEN) could cause SecureCRT to hang when connected via telnet. - The check for script filename extensions was case-sensitive. - Eliminated a rare, but possible GPF when closing SecureCRT. - Added a missing keyboard accelerator on the Emulation page. - A change in 3.0 (beta 8) caused the screen to be corrupted when viewing the scrollback buffer and then returning to the current screen. Changes in SecureCRT 3.0 (beta 8) --------------------------------- New Features: - The www.vandyke.com URL and support@vandyke.com e-mail address in the About dialog are now live. Changes: - In SSH2, on occasion, RC4 encryption could fail, resulting in the current SSH2 session being closed. - In SSH2, turning on "File / Trace Options" could result in internal buffering problems. - In SSH1 and SSH2, the password dialog now accepts control characters (Ctrl+H and Ctrl+V are still handled normally). - In SSH1, the password field has been removed from the "Connection" page in the Session Options dialog. - In SSH1, if password authentication fails, the connection is no longer closed. The user is prompted for the username and password. - Added seventh expect/send item on the "Login Scripts" page of the Session Options dialog. - ActiveX login scripts now start with synchronous true. Bug Fixes: - In SSH1, while using port forwarding, data being sent to the server could be dropped if the local socket sending the data was closed immediately after sending the data. - In SSH1, eliminated possible stalling in X11 forwarding. - In SSH1, the passphrase was being cached after closing the connection until a new connection was established or SecureCRT was closed. - If the current working directory wasn't the SecureCRT 3.0 directory, online help would not open. - Occasionally, opening a URL that included commas would fail. - In the Connect dialog, starting an in-place rename of a session and then clicking on "Properties" in the toolbar could result in copy a of the session being created. - In Telnet, when the connection was closed, any pending data received was not processed or displayed by the terminal emulator. - If SecureCRT was in full screen mode and minimized, restoring the window would result in SecureCRT being maximized. - A session's firewall setting was ignored when the session was started from command line with /S option. Changes in SecureCRT 3.0 (beta 7) --------------------------------- New Features: - Added global option for horizontal and vertical scrollbars. - Added global option "Buffer pass through printing". - Added "File/Print/Eject Page". - Added MENU_PRINT_EJECT_PAGE function. - Added MENU_PRINT_CANCEL function. Changes: - Support for SecureCRT 2.x script files has been restored. - When the Quick Connect dialog is shown, the initial focus is now on the hostname. Bug Fixes: - In SSH2, if the current passphrase was blank, the user would never be prompted for a new passphrase while changing the passphrase. - A GPF could occur when closing SecureCRT while connected to an SSH2 session. - Migrate.exe did not migrate SSH1 passwords. - Under Windows 98, it was possible the login script would be start again after login was complete. - When SecureCRT was in full screen mode, SecureCRT would not minimize when "minimize all" on the task bar was selected. - Selecting "File / Recent Session" from the menu did not open a new session if the current session was the "Default" session. - The Quick Connect dialog now shows the protocol defined by the "Default" session. Previous to this release, the Quick Connect dialog would default to telnet regardless of the "Default" session settings. - If a shortcut to SecureCRT was set to start SecureCRT minimized, the initial number of rows was when SecureCRT was restored could be incorrect. - In TAPI, several error messages where improperly formatted. Changes in SecureCRT 3.0 (beta 6) --------------------------------- New Features: - Added scrollbar functions SB_HALF_PAGE_UP and SB_HALF_PAGE_DOWN. Using the Keymap Editor, a key combination can be mapped to scroll the screen up or down a half page. Changes: - Changed SCO-ANSI to SCOANSI for both terminal and keyboard emulation. - In the Connect dialog, Alt+Enter now shows the session properties. - In SSH1, the /PASSWORD and /USERNAME options are no longer ignored if the /S option is used. - In SSH2, added ability to change passphrase for private key in Advanced SSH Options dialog. Bug Fixes: - For applications such as IRC, BitchX and Tiny Fugue, data scrolled off the top of the scrolling region was not added to scrollback buffer. - In both SSH1 and Telnet, if SecureCRT received a large amount of data over a short period of time, SecureCRT could hang. - Selecting text while SecureCRT was receiving data could cause SecureCRT to hang. - Turning Hold Screen on, then off could cause SecureCRT to hang. - "not connected" could be inserted into the window title more than once. - Tab order on several pages in the Session and Global Options dialogs was fixed. Because the tab order was incorrect, using some of the accelerators would cause the dialog to close. - SecureCRT could crash on startup when selecting some printers. Now, SecureCRT will report an error. - If SecureCRT was disconnected during a lengthy paste, the paste continued after an immediate reconnect. - Keyboard input could be sent to the remote system during a lengthy paste. - In a script, after the crt.session.connect() command established a serial session, no more script statements were executed. Changes in SecureCRT 3.0 (beta 5) --------------------------------- New Features: - Sessions and folders in the Connect Dialog can be manually ordered using drag and drop. - Added /PASSWORD command line option for SSH1 and SSH2. Changes: - In SSH2, don't prompt for passphrase until the server has acknowledged it can accept the public key. - In the Connect Dialog, Alt+Enter now shows the selected session's properties. - Added horizontal and vertical scroll bar options to the Window page under Appearance on the Session Options dialog. - When a session is disconnected, the previous title bar text is now preserved. - Changed color scheme in VMS profile to Traditional. - Added support for the "Menu" key in both the Connect Dialog and terminal window. - Changed maximum number of com ports from 20 to 50. - Removed minimum and maximum test for initial window position. This allows users to use SecureCRT on virtual desktops that depend on using positions larger than the physical display. - If there are no modems configured on the system when the TAPI config dialog starts, optionally starting the modem control panel to add a modem. Bug fixes: - In SSH2, data could be dropped at the end of a port forward session. - In the Connect Dialog, pasting a session a 2nd time would fail. - Occasionally, message box in a running script would not be displayed. - When no protocol was specified on the command line with a hostname, telnet was used by default. Now, the protocol specified by the default session is used. - If both "Automate Login" and "Login Script" are enabled, the automated log runs first. Once the automated login runs, the login script specified is run. - If "Recently used session list" is changed to 0, the sessions are now cleared from the configuration database. - Once "Always On Top" was on, switching to a new session would not turn the setting off. - Occasionally, changes made to a color scheme were not saved. - Occasionally, the first data received at login would be missed if the ActiveX login script was not yet completely initialized. - In the Connect dialog, SecureCRT would hang if clicked on new folder button and then immediately clicked on the delete button. - Multiple TAPI errors could occur if TAPI 2.0 was not installed. TAPI 1.x is now supported. Changes in SecureCRT 3.0 (beta 4) --------------------------------- New Features: - In SSH2, added support for specifying local and remote port forwarding on the command line. - Online help in HTML Help format. - New sample scripts in the scripts subdirectory. Changes: - Added support for SCO ANSI escape sequences CSI=nF , CSI=nG - Terminal output is now suspended while selecting text. - In VT100 emulation, the delete character is no longer displayed when received. Bug fixes: - In SSH2, "Forward X11 Packets" check box could change states. - In SSH2, Change default MAC to MD5. - In SSH2, typing before the connection was completely establish could hang the session. - In SSH2, there was short interval where a window size notification could be lost while establishing the connection. - In SSH2, the dialog used when changing to PublicKey authentication referred to RSA authentication in a couple places. - In SSH2, forwarded connection could send data that exceeded the current window size. - In SSH2, if a channel open request was rejected, under certain cirumstances, a GPF would occur. - In SSH2, if the server rejected the username/password, then the password dialog simply reappeared. The user is now notified about the server rejection. - In SSH2, if the window was resized during initial key exchange, then we could send a message to the server on an invalid channel, causing the server to disconnect us. - With ANSI color on, one more lines of garbage characters could be displayed if the terminal window size was changed. - A telnet connection could hang after receipt of IAC if next byte was OOB. This could happen when typing ctrl-C on some systems. - Using the VT220 keymap, pressing F1 (VT_HOLD_SCREEN) would hang the current telnet session. - Clicking on the terminal window could clear the current clipboard contents without a new selection being made. - The tab order on the global options page was incorrect. - Folders and sessions in the connect dialog were not sorted. - In Connect Dialog, if a "New Folder" was created and not renamed, it was not placed in the database and would not appear the next time the connect dialog came up. - SecureCRT would hang if the user copied an item in the connect dialog, deleted the item, and then attempted to paste that item. - A GPF would occur if two copies of SecureCRT were started that both open the same log file. - Occasionally, with line wrap off, the character in the last column would not be drawn. - Toggling the menu bar or chat window no longer changes the number of terminal rows. - Two error messages were not formatted correctly resulting in %1 being displayed instead of the correct text. Changes in SecureCRT 3.0 (beta 3) --------------------------------- New Features: - Added support in SSH2 for public key authentication (requires server 2.0.13). - Added new command line option for migrate.exe. Usage: migrate.exe SecureCRT [session_config_file_path] The session_config_file_path is optional. Changes: - Quick connect dialog remembers last set of parameters. - When copying session "X", the new session is now named "X(1)" instead of "Copy of X". Bug fixes: - In SSH2, if a saved password was incorrect, the user would not be prompted for a password, and the server would disconnect SecureCRT with an "Authentication Method Disabled" error. - In SSH2, on some systems, the "none" authentication did not return a list of valid authentication methods. SecureCRT now starts with the chosen authentication method, rather then sending none to find valid authentication methods. - In SSH2, added ability to connect to lsh, by selecting "Standard" mode. - In SSH2, in certain circumstances, first packet could be lost, causing the connection to hang on startup. - Migration would silently fail if the .CFG file was not found in the expected location. - During migration, all port forwarding settings were lost. - Migration would fail to migrate the correct keymap filename if the same filename was referred to by multiple sessions. - Renaming a session folder would fail where the new name is just the original name with differences in letter case. - A telnet connection could hang. Under most circumstances, the connection would work as soon as any key was pressed. - The command line option /MAX_COLS had no effect. - ANSI graphics state was incorrectly reset when SGR 0 was received. The result was that ANSI line drawing characters were not drawn as expected. This bug affected both ANSI and SCO ANSI emulation. - System menu commands restore and minimize did not work in full screen mode. - Toggling the menu bar on and off would change the number of terminal rows. - Send ASCII could hang. - Typing backspace while connected to non-telnet server (e.g. a MUD) would result in a GPF. - Changes to session when creating a copy were not correctly saved. Changes in SecureCRT 3.0 (beta 2) --------------------------------- Features: - Added an option to turn the "Flat toolbar" off Changes: - Significant performance increase for opening the connect dialog. - Added keyboard accelerators for connect dialog. - From the connect dialog, new sessions are now inserted in alphabetical order. - New 32x32 icon for SecureCRT - New 16x16 icon for SecureCRT - The MRU range for the file menu is now 0..9 (was 1..9) - Added Trace Options for rlogin - In addition to being a global option, Disable Resize is now a session option. - In addition to being a global option, Auto Reconnect is now a session option. Bug fixes: - Fixed all accelerators in options dialogs so there are no conflicts - e.g. &Port and &Profile on the Connection page. - Full screen mode was not handled correctly depending on the task bar state. - If an invalid port was entered, a warning was displayed and then the session dialog was prematurely closed. - "File / Reconnect" would fail after disconnecting from an SSH2 session. - Trying to open a new window using SSH1 or SSH2 would result in a command line error message being displayed. - SSH1 could stall causing the terminal session to be non-responsive. - In SSH1, the cipher drop down box was not disabled when connected. - In SSH2, fixed bug where the error "read newkeys is invalid" was incorrectly displayed. - In SSH2, fixed bug which caused "Bad local id in received WINDOW_ADJUST" error. - In scripting, a run-time error now occurs if you are disconnected while at a wait statement. - In scripting, Screen.CurrentRow, Screen.CurrentColumn, Screen.Send, Screen.SendSpecial, Screen.WaitForString, Screen.WaitForStrings, Screen.WaitForKey, Screen.WaitForCursor now report a runtime error if the session is not connected. - If the most recent script ran had an illegal filename, selecting "Script / Run" from the menu would fail. - In scripting, Window.Activate() did not bring SecureCRT to the foreground. - In scripting, Window.State did not return the correct value when SecureCRT was hidden. - The answerback string was sent in response to ctrl-E even if the answerback option was not turned on. - Connection closed dialog was not displayed. - SecureCRT icon now changes when connected and session is encrypted. - Loading the factory profile was a noop. - Script methods return boolean now return -1 (as required by VB automation) rather than 1. - Changing the maximum number of columns was not deferred until the next invocation of SecureCRT. The result was a GPF. - Occasionally, a small of amount of data from the remote system was be processed after SecureCRT thought the connection was closed. One result, was a flashing cursor when disconnected. Another result, was an occasional GPF. - Eliminated unnecessary save of *all* sessions when connecting - ANSI graphics characters were not being displayed correctly - Switching between protocols on the connection page no longer loses hostname, username, etc. - Depending on script, after the script would exit, SecureCRT would no longer process incoming data - ZModem upload under SSH1 would not start. - Under certain circumstances, the SecureCRT window would be displayed as transparent showing the desktop or applications beneath it. - WaitForString and WaitForStrings did not work with Synchronous off. - Color schemes were not being saved at the proper time. - Auto Session Page text said CRT instead of SecureCRT. Changes in SecureCRT 3.0 (beta 1) --------------------------------- New features: - SSH2 (in addition to SSH1) is now supported - ActiveX scripting support allows use of mulitple scripting languages include VBscript, JScript, and PerlScript - SCO ANSI terminal and keyboard emulation - The new connect dialog supports creating a desktop shortcut from the connect dialog. - A new "Auto Session" option allows you to specify the session to connect with on application startup. - Full screen mode is now supported. Use Alt-Enter to switch to and from full screen mode. - New global options include: - automatic reconnect - specify delay between characters on paste (or ASCII send) - specify delay between lines on paste (or ASCII send) - the number of recent sessions in the File menu (up to 9) - the maximum number of terminal columns (up to 512) - which web browser is used with "Open URL" - whether DDE is used to start the web browser Changes: - Session keyboard mapping now supports any key combination - not just function keys - without the need for an external keymap file - Printing options can be set globally or by session - The connect dialog has been completely redone. It now supports folders. Operations in the connect dialog are available from both the toolbar and the context menu. - The session and global options have been reorganized for easier access - All settings are stored in a common location. Previous to 3.0, global settings were stored in the registry and session settings were stored in CRT.CFG. - The scrollback buffer maximum has been increased from 9999 to 32000. In addition the scrolling performance as new data is received has been significantly increased.