May 23rd, 2012Changes:
· Custom log data is no longer inserted into raw logs.
Bug fixes:
· When the option "Scroll to clear screen" was off in a session, if the same session was opened again in another tab or cloned, the option was on in the new sessions.
· SecureCRT did not log Korean characters correctly.
· The lock icon was not displayed for locked sessions when the tab appearance was set to "Background colors". The tab is now changed to gray when it's locked.
· When the option to show the vertical scroll bar was off, if the application window was maximized and a session was opened in a tab and cloned, the cloned session was blank.
· If a tab title was changed via an xterm escape sequence and then the "Session Options" dialog was opened and closed, the tab title was changed to the session name.
· If the toolbar was hidden or the Connect bar was removed from the toolbar, SecureCRT would crash when attempting to display the "View" menu.
· After sending a tiled session to a new window, switching to tabbed mode, and then dragging the session back to the original window, the session name was not displayed.
· If the "Default" session was configured with an incorrect password and the option "Display logon prompts in terminal window" was set, the session failed to connect instead of prompting for the correct password.
May 4th, 2012New features:
· Added the ability to tile sessions within the SecureCRT application window. Sessions can be tiled vertically, horizontally, or cascaded. Scripts can use the "Tab" object to work with tiled sessions.
· Added the ability to start a built-in TFTP server when a session connects.
· SSH2: Added the ability to skip authentication methods while authenticating.
· When the mouse hovers over a button, the command the button is mapped to is shown as hover text.
· Added the ability to map the items on the "Tools" menu to a button or key.
· Added the ability to map "Always on Top" to a key.
· Added support for the "Insert" key to the Wyse 50/60 emulation.
· Windows: Added a global option to ignore the print screen (PrtScn) key being pressed.
Changes:
· Improved the performance of the "Connect" dialog when the configuration is located on the network.
· It is now possible to close the last tab.
· The port can now be specified in the "Connect" bar on the toolbar.
· The chat window history limit has been increased to 32,000 commands.
· When scrolling back into the scrollback buffer, empty lines (such as from the "clear" command) are not shown.
· Added a way to access buttons that were not visible on the button bar if the configured buttons did not fit in the window.
· Added "Send Break" to the "Edit" menu, which sends a Telnet break.
· If a change is made to the settings of a cloned session, the change is propagated to the other SecureCRT windows and/or sessions.
· The first tabbed session's scrollbar settings are used for subsequent tabbed sessions so that all the sessions will have the same number of rows and columns.
· When attempting to use Zmodem to transfer a file larger than 4 GB, an error is reported.
· The installer now remembers the installation options from the previous install.
· Kerberos delegation results are displayed in the trace output.
· The script file location is displayed when a script cannot be opened.
· The "Connect" dialog now has the same icons as the toolbar.
· Changed the button labels on the dialog that is displayed when the default session is changed in order to make it harder to accidentally apply the changes to all sessions.
· Telnet: When the session's IP address is IP4, it is displayed in the status bar.
· When there are multiple tabbed sessions, only the active session is displayed in the Windows 7 task bar preview.
Bug fixes:
· SecureCRT crashed when a script was run that sent an exit command to an SFTP tab.
· SecureCRT crashed if a script called GetOption("[SSH2] Port") on a session that did not specify a firewall.
· If a command was typed at the prompt, but ENTER was not pressed, and then the session was scrolled back to the oldest row and the top row was selected and ENTER was pressed, SecureCRT could crash.
· SecureCRT crashed when the "Retain size and font" session option was set, the lines of scrollback was set to 0, the visible rows were less than the actual number of rows, the first several rows were not visible, and an escape sequence that erased a line was sent.
· Xmodem transfers could hang at the beginning of the transfer.
· If a host key hostname contained an escaped ".", it could not be saved.
· When using mouse mode in vi, vim, or mc, there was a slight delay between clicking the mouse and the cursor being positioned at the mouse location.
· When scripting was administratively prohibited, the "Script" menu was still available.
· When the global option "Reuse disconnected tabs" was set and a session that had the "Show chat window" and "Sync view to size" options set was disconnected and then a session with "Sync view to size" enabled, but "Show chat window" disabled was connected, the number of rows in the session was not correct.
· When a key was mapped to a function or arrow key that sent a multi-byte escape sequence, the mapped key sometimes didn't work.
· The title bar setting in the "Default" session could be used to rename tabs using substitution parameters for "Quick Connect" sessions, but was not honored for saved sessions without a username.
· The "Quick Connect" dialog sometimes used the default username or previously used username even though the username was empty.
· The keyboard-interactive password prompt was displayed when the password was specified on the command line with the /PASSWORD flag.
· If a log file contained a leading space, an error was reported.
· The keyboard accelerator for "Clear Screen and Scrollback" did not work from a custom menu.
· If there were two tabbed sessions and there was scrollback data in the second tab and then the second tab was disconnected and reused for a different session, the scrollback was not cleared.
· When Zmodem was used to transfer a file larger than 2 GB, the progress information was not correct.
· If /Log was specified on the command line and additional parameters such as session name or username were also specified, the /Log parameter was not honored.
· If Connect() was called from a script and the option to suppress popups was set, it was not possible to detect failures by looking at error codes in crt.GetLastError and crt.GetLastErrorMessage.
· SSH1/SSH2: If key re-exchange occurred during a transfer and "zlib@openssh.com" compression was being used, the session disconnected.
· SSH2: Authentication failed when the server requested the keyboard-interactive method more than once.
· If the Windows Input Method Editor (IME) was being used to input Korean characters and data was received, the IME was cancelled, causing the wrong character to be inserted into the session.
· When a session name was longer than 32 characters, it was listed twice in the Windows 7 Start menu and taskbar MRU list.
· On Windows 7, if the system Telephony service's startup type was set to "Disabled", a TAPI error was reported when attempting to create a session using the session wizard.
· In the Chinese version of Windows XP and Vista, the font used for the title bar, menu, and status bar was smaller than the system font.
· On Windows XP, the button bar dropdown sometimes displayed the button bar names in a larger than normal font.
April 20th, 2012Bug fixes:
· When the emulation was set to "Xterm" and the option "Send scroll wheel events to remote" was set, in vi or vim, it was not possible to scroll down using the mouse scroll wheel.
· When the system used the Microsoft HID-compliant mouse driver and the mouse was configured to scroll one screen at a time, SecureCRT did not scroll the correct direction when the mouse scroll wheel was used.
February 3rd, 2012Changes:
· This version of SecureCRT is not compatible with older versions
· of the Activator and older versions of SecureCRT are not
· compatible with this version of the Activator.
Bug fixes:
· SecureCRT could crash while idle when several Telnet sessions
· were connected.
· SecureCRT crashed if a tabbed session was disconnected while a
· script was running.
· The URL syntax of telnet: did not work.
· If an attempt to run a script in a locked session was made,
· SecureCRT incorrectly reported that a script was already running.
· Windows: On Windows 7, if a second binary transfer was attempted
· after the first binary transfer completed, nothing was transferred.
· Windows: If the "SCRTMenuToolbarV2.ini" file was corrupted,
· SecureCRT crashed on startup with a Windows runtime error.
· Mac: Keys mapped to MENU_WINDOW_NEXT and MENU_WINDOW_PREV were
· not saved correctly.
· Linux: On Ubuntu, SecureCRT crashed when attempting to establish
· an SSH2 connection to a local or remote host.
· Linux: When Ubuntu ran on a system with an older processor, such
· as Pentium 4 or Pentium M, SecureCRT crashed when attempting to
· connect to a Secure Shell server.
November 10th, 2011Bug fixes:
· If the default session was edited and the changes were written to all sessions, the logon actions were set to the default for all SSH2 sessions regardless of whether or not the logon actions had been changed.
· If a script was running in a tabbed session and the tab was closed while the script was running, a script cancel error was reported.
· With the "Show confirm disconnect dialog" option on, if a script was running and "Disconnect" was selected from the menu or toolbar and then the disconnect operation was cancelled, the script was stopped anyway.
· Telnet: When CTRL+S was used to suspend output, the CPU usage went to 100%.
August 12th, 2011Changes:
· Windows: The 32-bit installer can be installed on a 64-bit system.
Bug fixes:
· Xmodem transfers failed over connections using the Raw protocol.
· The hostname was not saved in sessions that used the Raw protocol.
· The item MENU_GOTO_CONNECT_BAR did not work when it was mapped to a button on the button bar.
· The Connect dialog allowed connect attempts to sessions with the protocol set to "None".
· The extend evaluation feature did not work correctly. After the offer was accepted, there was no button to extend the evaluation on the "Enter License" dialog as described in the instructions that had been e-mailed.
· Telnet/RLogin: On Windows 7, when multiple sessions were running in different windows such that they were separate processes and command output was streaming in them, one or more of the connections could get reset.
· Windows: On 64-bit machines, if the menu or toolbar was customized in SecureCRT 6.0 and then version 6.7 was run and "Yes" was selected after the prompt "Would you like to update the toolbar and menu bar?" was displayed, SecureCRT crashed when it was closed.
· Windows: When the SecureCRT window was restored after being maximized or in full screen mode, it was restored to the wrong size.
June 17th, 2011Bug fixes:
· If buttons were added to a new button bar and then an attempt was made to switch to a different button bar, SecureCRT could crash.
· When Ymodem was used to transfer multiple files, only the first file was transferred correctly and sometimes the error "Invalid access to memory location" occurred.
· In the Quick Connect dialog, if the port number was changed to something other than the default, the port number was reset to the default the next time the Quick Connect dialog was opened.
· Windows: If a USB serial adapter was removed while the serial session was connected, SecureCRT could crash.
· Windows: When the Windows 7 Areo snap feature was enabled, if the SecureCRT window was dragged so that it snapped to the side of the desktop and focus was switched to another application, when SecureCRT was restored from the taskbar, it reverted to its previous size.
· Windows: If the Windows 7 Aero snap feature was enabled and SecureCRT was dragged by the title bar so that it was maximized using the snap feature, the SecureCRT window was partially off screen.
May 27th, 2011Bug fixes:
· The SHIFT+INS paste accelerator did not work when a custom menu (.MNU) was being used.
May 19th, 2011Bug fixes:
· If "/POS" was the only option specified on the command line, SecureCRT attempted to use the last argument as the remote host.
· If the SecureCRT window was resized and trace options were on, the event was traced.
May 5th, 2011Bug fixes:
· SecureCRT could crash on exit due to the way threads were being cleaned up.
· SecureCRT crashed if a session with the "Auto reconnect" and "Close on disconnect" options enabled was disconnected.
· SecureCRT crashed after pressing OK on the "Session Options", "Lock Session", or "Confirm Disconnect" dialog if the session that launched it had been closed after the dialog was displayed.
· SecureCRT crashed after pressing OK on a script dialog if the session that launched the script had been closed after the dialog was displayed.
· When the /F parameter was used on the command line to specify the location of the configuration folder and the menu or toolbar was customized, the changes were not saved.
· A pop-up error message was displayed if the script method GetOption() was called with an unknown option name.
· Serial: After connecting to a Windows COM port and then pressing any key, the CPU was pegged.
· SSH2/SSH1: When a session established a port forward that launched an application, if the session attempted to connect using both an IPv4 and IPv6 address, two instances of the application were launched.
· Windows: On Windows XP, if the display theme was set to Blue, Black, Aqua, or Silver and more than one SecureCRT window was connected to a session and "Send chat to all tabs" was used to send text to one of the sessions, it caused the other window to freeze.
April 26th, 2011· SecureCRT could crash on exit due to the way threads were being cleaned up.
· SecureCRT crashed if a tab was closed while the tab context menu was being displayed.
· In Python, if ReadString was called with a number, SecureCRT crashed; and if it was called with no parameters, an error was reported.
· If SecureFX was installed with SecureCRT and SecureCRT was launched with a command line that specified an SFTP or FTP URL, SecureCRT crashed.
· It was not possible to read or set session printer options from a script.
· SecureCRT crashed if a Python script was running when SecureCRT exited.
· If a VBS script that called Crt.Sleep was cancelled, an error was reported.
April 13th, 2011Bug fixes:
· If the Connect bar was removed from the toolbar through customization and then SecureCRT was restarted, attempting to bring up the customization dialog caused SecureCRT to crash.
· If a script that called Crt.Screen.Send() was repeatedly run, it could cause terminal corruption and possibly a crash.
· Under certain circumstances, after editing the Default session and attempting to apply the changes to all sessions, SecureCRT hung.
· Scripts that called Crt.Screen.Send() to send end of line characters had different behavior than they did prior to version 6.7.
· After pressing the ALT key and then the ENTER key, SecureCRT attempted to connect to a host named "".
· When the SecureCRT window was resized by dragging the mouse, the rows and columns displayed in the status bar were not updated until the mouse button was released.
· If the Connect bar was removed from the toolbar through customization and SecureCRT was restarted, the Global Options dialog incorrectly showed that the Connect bar was visible.
March 25th, 2011Connect bar:
· The Connect bar provides a text entry box to connect to a session quickly without opening a dialog. The Connect bar supports SecureCRT command-line options.
Scripting enhancements:
· Script recorder adds Python support: Automate connections and routines using the Python script recorder, which records keystrokes and then generates a Python script.
· "Run Script" from a key or button: Map a key or button to browse for a script to run.
· New scripting functions: The FileOpenDialog() function opens a file browser and returns the selected file. ScriptFullName() returns the full path and filename of the currently running script. The Connect() function adds an optional parameter to allow pop-up messages to be suppressed.
Button bar enhancements:
· Add more than ten buttons to a button bar, copy and paste buttons from one button bar onto another, and move buttons within a button bar.
March 9th, 2011New features:
· Linux versions for Ubuntu 10.x (32-bit and 64-bit) and Red Hat Enterprise Linux 5.5 (32-bit and 64-bit).
· Added an optional connect bar, which allows a connection to be made by entering the host on the toolbar.
· Added support for recording Python scripts.
· Added the ability to add more than ten buttons to a button bar.
· Added the ability to copy buttons from one button bar and paste them on another button bar.
· Added the ability to move buttons within a button bar.
· Added the ability to map a key or button to browse for a script to run.
· Added the ability to configure the double-click tab action to be "Clone Tab in New Window".
· Added an option to the Connect dialog to sort sessions logically, which is helpful when session names contain numbers.
· In the Session Options dialog, added ability to sort columns in the Connection / Port Forwarding category.
· Added support for in-line composition of IME characters so that IME characters are inserted into the session window as they are typed.
· Added the script function FileOpenDialog() that displays the file browser and returns the selected file.
· Added the script function ScriptFullName() that returns the full path and filename of the currently running script.
· Added an optional parameter to the scripting function Connect() that allows pop-up messages to be suppressed.
· Added the ability to specify a listening IP address when setting up a local or remote port forward from the command line.
· Added a global INI-file-only option "Script MRU Count" that allows the number of scripts displayed in the recently used script list to be specified.
· When the global INI-file-only option "Single Instance" is set and SecureCRT is already running, shortcuts that use the /S flag now open the specified session in a new tab.
· Windows: Environment variables can be specified when assigning a "Run Script" or "Launch Application" function to a button or key.
Changes:
· Line and character send delay settings are now honored for buttons and keys mapped to send strings.
· When pasting text into SecureCRT, LF is converted to CRLF.
· The session option "Enforce X11 Authentication" can now be set in the Session Options dialog. Previously, it had to be set manually in the session .INI file.
· The button and keymap Menu function MENU_TAB_NEXT now has the same behavior as pressing and releasing CTRL+TAB. The Menu function MENU_TAB_PREV now has the same behavior as pressing and releasing SHIFT+CTRL+TAB.
· If a script is already running and an attempt is made to run another script, a message is displayed.
· Windows: Entering the license data now registers the application for all users instead of only for the current user.
Bug fixes:
· If SecureCRT closed while a dialog was being displayed, it crashed.
· If an escape sequence that sent a large file (1 MB or larger) was running and SecureCRT was exited during the send, it crashed.
· If a script set a session's columns to be larger than the maximum number of columns and then that session was used, SecureCRT crashed.
· SecureCRT could crash if it was in the process of closing and a script attempted to access an object that no longer existed.
· SecureCRT could crash when a second instance was started.
· SecureCRT terminal locked up after exiting a remote command such as "vi" or "man" if the window was resized while the command was running.
· Python scripts that contained a Unicode character in the script name could not be run.
· In some cases, screen reading software such as JAWS was not able to track the cursor when the cursor style was set to "Block". If the "Use trackable insertion carat" option is set, the "Vertical Bar" cursor style is now used.
· If a key or button was mapped to launch an application that did not have an ".EXE" file extension and an argument was specified, the specified argument was not saved.
· If a session used ANSI color and a color scheme and the scrollback buffer contained text, if ANSI color was disabled and re-enabled, some characters in the scrollback buffer were displayed using incorrect foreground and background colors.
· Highlighted text sometimes flickered.
· In the Connect dialog, if the right mouse button was clicked on title bar or toolbar, the context menu was not displayed at the mouse cursor.
· Telnet: When an unrecognized IAC SB option was received, garbage was displayed in the session.
· SSH1/SSH2: On Windows Vista and Windows 7, if "localhost" was specified for port forwarding, it resolved to an IPv6 address, which caused the port forward to fail.
· SFTP: In the SFTP tab, when an "ls" command was issued and the files had long names, the spacing of the output was not correct.
· SFTP: In the SFTP tab, tab completion did not work with character encodings such as utf-8, koi8-r, and OEM=cp866.
· Windows: When a Perl script was specified on the SecureCRT command line, an error was thrown if the script called Crt->Quit().
February 1st, 2011Changes:
· SSH2: Added support for reading AES-128 public keys.
Bug fixes:
· 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.
· 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.
· Under certain conditions, a race condition between terminating a script and closing SecureCRT could cause a crash.
· SecureCRT could crash if shortcut keys were used to select invalid operations in the Connect dialog.
· During initialization, if SecureCRT failed to acquire a Cryptographic Context, SecureCRT crashed when it closed.
· 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.
· When a local port forward contained an IPv6 address, SecureCRT was not able to save the host key.
· The session option to disable pass-through printing was not being honored.
· If two tabbed sessions were opened, but not connected, when the first tab was made active, its status indicator showed that it was connected.
· 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 a remote login banner contained a high-bit character, SecureCRT stopped displaying the banner when it hit that character.
· After loading an invalid keymap, pressing CTRL+TAB to switch between tabs no longer worked.
· Attempting to save a recorded script to a location that was not writable failed silently, causing the script to be lost.
· No screen painting occurred while crt.Sleep() executed in a script.
· The session option "Keymap v3" could not be accessed from a script.
· The script function crt.Session.Connect() always opened a new tab even when the "Reuse disconnected tabs" option was set.
· In Python scripting, the failSilently parameter in the ConnectInTab function in the Session object was not implemented.
· The script function SendKeys() did not send text to the correct tab if the tab was switched while the script was running.
· Selecting "Check for Updates" from the Help menu launched the VanDyke forums.
· Serial: If a session was disconnected during a Zmodem upload, SecureCRT could crash.
· Serial: SecureCRT could lock up if the session was disconnected during the Zmodem transfer.
· Telnet, Raw: If an invalid port was entered in the New Session wizard and the Back button was pressed, SecureCRT crashed.
· SSH2: It was not possible to specify the same port for port forwarding even if a different local IP address was used.
· In some cases, the initial position of a session was different when the session was disconnected and then connected again.
November 5th, 2010Changes:
· MENU_RECEIVE_BINARY was removed from the Map Selected Key dialog's Menu Function list because it is not currently supported.
Bug fixes:
· Toggling the chat window while a connection was being made could
· cause SecureCRT to crash.
· SecureCRT could crash after running for approximately 5000 hours or in less time if a large number of X/Y/Zmodem transfers were performed.
· If a session specified a line send delay and character send delay, the line send delay was also used as the character send delay.
· Windows: In order to display a single ampersand character (&) in the button bar, it was necessary to use four ampersand characters. This was inconsistent with versions prior to 6.5, which only required two ampersand characters.
October 22nd, 2010· If two different sessions were open and they used different button bars and then the chat window was opened in one of the sessions, its button bar was changed to the other session's button bar.
October 1st, 2010Changes:
· In Python scripting, case is ignored for the language specifier.
· SSH2: Remote password change requests are logged in the trace output.
· TAPI: Improved error message to be more informational when the COM port is already in use.
Bug fixes:
· In the Connect dialog, if a new folder was created and the Delete button was pressed while the folder name was still in edit mode, SecureCRT crashed.
· In the Connect dialog, if an attempt was made to paste a session that had been previously deleted, SecureCRT crashed.
· In a script, calling crt.Sleep after crt.Screen.Synchronous and crt.Screen.Send caused high CPU usage.
· When SecureFX was also installed, if the Global Options dialog was closed when the Terminal/Advanced category was active and the Global Options dialog was restarted, the active category was File Transfer/Options/Advanced.
· SFTP: The execute escape sequence "sftp-download" failed if the filename contained any spaces.
· Windows: If multiple SecureCRT windows were open and all the windows were closed by closing the Activator, SecureCRT could crash.
· The session tab text was cut off when the Windows system setting to use large or extra large fonts was used.
September 17th, 2010Changes:
· Added documentation for Python scripting.
· Windows: Added a Global.ini-file-only option to make the tab bar taller, which prevents the session name from being cut off in the tab when the Windows
Bug fixes:
· SecureCRT could crash when a binary file was sent using Send ASCII.
· In a script, when ConnectInTab was called without a hostname, the script would hang.
· If a script was used to change the port forward settings for the session that launched the script, the settings were not saved.
· In Python scripting, WaitForStrings and MatchIndex returned a 0-based index instead of a 1-based index, which made it difficult to distinguish between a timeout and the first string being matched.
· In Python scripting, the ReadString or WaitForStrings methods did not return the text up to and including the matched string.
· After printing a document, if the print margins were not the minimum size, they were changed to the minimum.
· SSH1/SSH2: When accessing the host key database, it was locked for writing, which could cause the host key database to be unavailable, particularly when multiple connections were scripted.
August 18th, 2010Changes:
· The Edit menu displays the appropriate hotkeys for Copy and Paste depending on what the "Use Windows copy and paste hotkeys" option is set to for the active session.
· SSH2/SFTP: Socket write errors are now written to trace output.
Bug fixes:
· If a session was disconnected during key exchange, SecureCRT crashed.
· If Crt.Quit was called from a Python script, a race condition was introduced, which could cause SecureCRT to crash.
· If the Find dialog was open for a tabbed session and then another tab was activated, the Find dialog had focus.
· If several sessions and SFTP tabbed sessions were connected and then the SFTP tabbed sessions were disconnected and reconnected, the tab status indicator and/or menu items sometimes did not reflect the correct connect status.
· In the Global Options dialog, in the Printing category, if the left margin was changed to an invalid margin, the top margin was also changed.
· When using X11 mouse positioning, if the global option "Paste on middle button" was set, the context menu was displayed in addition to the paste operation.
· Telnet: When CTRL+S was used to suspend output to the terminal, there was a significant delay (at least ten seconds) before output was suspended.
· Telnet: Send binary did not work.
· Windows: Dragging the "Send chat to all tabs" title bar up to the main application window caused SecureCRT to crash.
· Windows: The menu item "Go to Session Window" was never toggled to "Go to Chat Window".
· Windows: When the "Hide pointer while typing" option was set and typing was done in another application, when the mouse was moved to the SecureCRT window, the mouse pointer was not displayed sometimes.
August 11th, 2010Bug fixes:
· When multiple instances of SecureCRT were running, attempting to display a connection closed message could cause SecureCRT to crash.
· SecureCRT could lock up when a Send ASCII command was used to send a large file (e.g., 100,000 lines).
· SecureCRT hung when attempting to open the Customize dialog if multiple instances of SecureCRT were running.
· In some cases, when characters with diacritics were pasted into a session using VT220 emulation, they were not displayed correctly.
· The way characters were clipped when they were displayed in the session affected the behavior of the JAWS screen reading software.
August 4th, 2010New features:
· SecureCRT for Mac OS X delivers right out of the gate, with reliable, mature terminal emulation, tabbed sessions, security, powerful session configuration, and printing support.
· SecureCRT for Mac OS X adds support for the local command shell.
· Added embedded support for the Python scripting language.
· New Raw protocol mode allows for no (or little) interpretation of data from the remote system, which is helpful for troubleshooting.
· Added a "Send Binary" transfer option.
· A unique log name is automatically generated when the specified name is in use (e.g., cloned or SFTP sessions).
· Arguments can be passed to scripts from buttons and mapped keys.
· Added new double-click options to tabs; these options are "Send Tab to New Window" and "Reconnect Tab".
· On Windows, the button bar can be positioned at the top of the SecureCRT window.
· Added an option to kill the tab created by the ConnectInTab script function when it fails to connect to a host.
· SSH1/SSH2: Added support for the "null" host-key algorithm for GSS-KEX as specified in RFC 4462.
Changes:
· Added "Manage Agent Keys" to the Tools menu.
· When the "Trace Level" is set to 9, the password is automatically redacted from the trace output.
· In the Quick Connect dialog, if the protocol is changed from SSH1 or SSH2 to any other protocol, the port is changed to the default port.
· In the Global and Session Options dialogs, the options in the Advanced Printing category were moved to the Printing category.
Bug fixes:
· If "\p" was specified in an anti-idle string, SecureCRT could crash after the string was sent.
· If a tab completion was cancelled on a slow server and then the connection was closed, SecureCRT could crash.
· When sessions were cloned using "Clone in New Window", configuration information could potentially be written at the same time, causing SecureCRT to crash.
· SecureCRT opened an SFTP channel when opening the Session Options dialog, which could cause the active session to disconnect.
· If SecureCRT was launched more than once on the same machine using different configuration folders and a session that existed in one configuration, but not the other, was opened in the Activator, the instances of SecureCRT that did not contain the session crashed.
· Quick Connect sessions where the host was an IPv6 address could not be saved.
· The blink attribute was not honored when the SecureCRT window was maximized and the cursor was outside the session's original geometry settings.
· Dismissing the Find dialog in a different tab than it was started from could cause output to suspend.
· When the option "Only show tabs when there are more than one" was enabled and a second tab failed to connect, the tab bar was not displayed.
· When multiple sessions were edited at the same time, port forward changes were not always saved correctly.
· In the Printing category in the Global and Session Options dialogs, invalid margins could be saved.
· Cloning a non-SSH2 session in a script caused the script to hang.
· In the ReceiveXmodem script function, the "Download" folder was not honored.
· If the scripting clipboard format was set to an invalid format, the last error was not set correctly.
· The CRT.Session.Connect script method did not allow a script to capture in-terminal SSH2 username or password prompts.
· If SecureCRT was displayed on a second monitor when it exited and only one monitor was available the next time it ran, SecureCRT was still displayed on the second monitor.
· If full-screen mode was entered before a session was connected and then full-screen mode was exited, the SecureCRT window was displayed partially off screen.
· On the 64-bit version of Windows 7, tab preview functions did not work.
· On Windows, when large font (120 DPI) was used, text on some dialogs was truncated and buttons on the Keymap Editor dialog were cut off.
· If an X11 error occurred, the error message was displayed behind the SecureCRT window.
· Serial: The XOFF setting was not being honored, which could cause input to go to the wrong session when more than one Serial session was connected.
· SSH1/SSH2: If an accept host-key prompt was displayed during key exchange and the protocol NOOP anti-idle expired, the SecureCRT window could hang.
· SFTP: SecureCRT crashed when trying to open an SFTP tab if the remote server did not support SFTP.
· SFTP: Memory was leaked when SFTP tabs were closed.
May 12th, 2010Changes:
· After changing the selected button bar in the drop-down list, focus is returned to the active session.
Bug fixes:
· SecureCRT could become unresponsive when switching from an RDP session to a local session.
· Fixed threading issues that could cause SecureCRT to crash.
· SecureCRT could crash when it was in full screen mode and random data was received.
· SecureCRT crashed if a logon script called Disconnect() followed by Connect().
· With multiple SecureCRT windows open, toggling the chat window, button bar, etc. caused the terminal size to get smaller and could cause SecureCRT to crash.
· SecureCRT could disconnect from a Cisco router if data was sent before the shell was ready.
· SecureCRT could crash when attempting to connect to a session using a hostname that could not be resolved.
· Enabling GB18030 Simplified Chinese character encoding caused the session to stop displaying output.
· The performance of "Send ASCII" decreased significantly as the number of lines being sent increased and SecureCRT could appear to be hung.
· Line-drawing characters were not displayed correctly with SCOANSI emulation.
· Artifacts were sometimes left on the screen when ClearType was enabled.
· If a non-qualified path was specified for the log file, SecureCRT failed to log and did not report an error.
· If the Close button was pressed a second time for a session to a slow or unresponsive server, the connection was orphaned and would not close until SecureCRT exited.
· If the button bar drop-down list was selected, typing the first letter of a button bar name caused the button bar height to increase.
· If the session's tab was clicked, focus was not placed in the terminal area of the session.
· The arrow keys could not be used to navigate context menus.
· SSH1/SSH2: SecureCRT could crash if a session was disconnected during user authentication.
· SSH1/SSH2: After changing a port in the port forwarding settings in the default session and applying it to all sessions, the
· setting was removed altogether.
· SSH1/SSH2: If a session was connected more than once and the session's port forward options were modified, the changes were not saved.
March 11th, 2010Changes:
· The SecureCRT version in the Windows uninstall "DisplayVersion"
· registry key now contains the point release number in addition
· to the major and minor version numbers.
· For Zmodem transfers, "Zcommand received" messages are displayed
· in the session window rather than in a message box.
Bug fixes:
· SecureCRT could crash when connecting multiple tabs in a script.
· SecureCRT could hang when the UNIX "tail" command is running on
· a busy file and the user right-clicks on a selection.
· SecureCRT could hang when right-clicking a URL that spanned more
· than one line.
· If the character encoding was set to "None", SecureCRT crashed
· when attempting to do a Zmodem, Xmodem, or Ymodem transfer.
· Zmodem failed to transfer files that contained characters that
· are not valid in Windows filenames.
· On Windows 7 and Vista, if an application that disabled and
· re-enabled Aero (such as NetMeeting), the SecureCRT window was
· not drawn correctly when it was restored.
· On Windows 7, when a session was restored from the taskbar after
· using live preview, the cursor was not displayed in the session.
· When the Windows ClearType setting was off, SecureCRT displayed
· ClearType text.
· When the tab width was reduced because a large number of tabs
· were displayed, there was a large gap between the last tab and
· right side of window.
· SSH1/SSH2: After changing a port in a port forward item in the
· default session and applying the change to all sessions, the
· port forward item was removed altogether.
January 22nd, 2010Changes:
· Under Windows 7 and Vista, removed the prompt for making SecureCRT the default Telnet application since many applications, such as Internet Explorer 8, do not allow Telnet
Bug fixes:
· If SecureCRT was in the process of closing and the close button was pressed again, SecureCRT could crash
· SecureCRT could crash when printing to an Adobe PDF printer using pass-through printing
· If the global options "Use trackable insertion caret" was set, the cursor did not blink
· If SecureCRT and SecureFX were integrated and the terminal or file transfer protocol was changed to "None", the change was not saved
· In the Key Generation wizard, if a key was generated and then the user clicked "Back", changed the size of the key, and answered "Yes" to the prompt about regenerating the key, the key was not regenerated
· The menu was not expanded when the ALT+ key was pressed
· If a line of text that contained an end-of-line character was copied and pasted, the end-of-line character was not included
· If a URL contained international characters and the URL was opened using "Open URL" or CTRL+, the URL was cut off before the first international character
· On Windows 7 and Vista, if a previous version of SecureCRT was running prior to installation and the installation option
· "Automatically close and attempt to restart applications" was selected, the previous instance of SecureCRT was not closed and could only be closed from the task manager
· On Windows 7 and Vista with Aero enabled, if a custom menu was used, the Close button on the main SecureCRT window appeared to be disabled even though it was not
· Serial: Disconnecting and reconnecting the physical RJ45 cable connector caused SecureCRT to crash
December 10th, 2009Bug fixes:
· SecureCRT could crash if the application's Close button was pressed more than once.
· If a key was mapped to a string that contained "p" (pause), SecureCRT crashed when the key was pressed in the terminal window.
December 3rd, 2009Bug fixes:
· If a .XML custom menu and toolbar file contained a menu on the toolbar, SecureCRT crashed when trying to import it into version 6.5.
· SecureCRT could crash if text was double clicked while session output was scrolling and was more likely to occur if the scrollback lines were set to 0.
· If invalid parameters were passed into the script function Screen.Get2, SecureCRT crashed.
· On Windows 7, if the Global.ini option "Disable Aero Peek" was enabled and an Auto session was specified, SecureCRT crashed on start up.
· On Windows 7 and Vista, if the option "Only show tabs when there are more than one" was set and a session was connected and then that session and another were opened in a new window, the first session shrunk by two rows.
· If the global option "Only show tabs when there are more than one" was set and a second session was connected, the tab status indicator for the first session showed that it was disconnected even though it was connected.
· When "ANSI Color" was off, some of the vttest "double-sized characters" tests did not display correctly for VT100 sessions.
· If the SecureCRT cursor was blinking or there was blinking text displayed in the session and a menu was activated, the cursor and text stopped blinking.
· If a column selection was made, after releasing the ALT key, focus switched to the menu.
· If two SecureCRT windows were open in separate processes, if the display theme was changed, the toolbar was not always updated to the new theme in the other windows. The script function Screen.Get2 only returned the first
· character.
December 3rd, 2009Changes:
· VRALib: Added the function "GetConfigValue" to the Connection object which when called with the string "Enable FIPS Mode" will allow a VRALib script to determine whether or not FIPS mode is enabled.
Bug fixes:
· Removing a user from the Virtual Root access control list could have caused the path and alias fields to be cleared.
· VShell FTPS: Authentication of VShell internal user database users could have failed even with a valid password.
October 29th, 2009Changes:
· Restored previous behavior of allowing the password to be saved
· regardless of the "Auto Save Options" setting.
Bug fixes:
· It was possible for SecureCRT to crash when attempting to select
· text near the end of a line.
· SecureCRT could crash when configuring a private key for a
· session.
· SecureCRT could crash when a tab was closed if the Session
· Options dialog had been opened after connecting to a session.
· If the INI-file only option "Force Close On Exit" was set and
· an SSH2 session was connected and cloned, if one of the tabs was
· closed, SecureCRT crashed on exit.
· Displaying certain Unicode sequences could cause SecureCRT to
· hang.
· Scrolling Unicode data was much slower than scrolling non-Unicode
· data.
· The underscore character was included in the list of default
· delimiters.
· If the user had full write access to the root drive and
· attempted to log to a file in the root drive, an "Access Denied"
· error was reported.
· Send ASCII ignored the end-of-line characters if the text file
· contained end-of-line characters other than CRLF.
· Clicking the red "X" in the Windows 7 taskbar peek for SecureCRT
· did not close SecureCRT.
· On Windows 7, if ANSI color was on and a tab subsequent to the
· first tab was connected, the terminal area in the new tab
· flickered, briefly showing lines of different colors.
· When the JAWS screen reading software was used in cursor mode,
· if output that contained blank lines was displayed in SecureCRT,
· using the arrow keys to move the mouse cursor over the blank
· lines caused the cursor to jump over several blank lines instead
· of moving one line at a time.
· After upgrading to 6.5, if a custom menu and toolbar XML file
· from version 6.2 or earlier existed, the ALT+B accelerator to
· connect in a tab no longer worked.
· If the global option "Show confirm disconnect dialog" was off
· and a session was connected and cloned, then the cloned session
· was closed using the close button on the tab, window decorations
· such as menus and toolbar buttons did not receive focus when
· mousing over them.
· Output that did not wrap when printed under Windows XP wrapped
· when printed under Windows 7 and Vista.
· Bold characters were not printed as bold characters.
· SSH2: Attempting to use a private key without a corresponding
· public key caused SecureCRT 6.5 beta 2 to crash.
· SFTP: SecureCRT could crash when downloading a directory that
· contained thousands of files.
October 16th, 2009New features:
· The chat window can be resized by dragging the splitter bar.
Changes:
· SSH2: When an RSA key is used for authentication, only the
· private key is required, which makes it easier to use Amazon
· EC2 keys.
· If a custom menu (.mnu) file specifies the "Office 2007" theme,
· which is not available in SecureCRT 6.5, the "Office 2003" theme
· is put in the menu instead.
Bug fixes:
· If the Activator was exited while the Global Options dialog was
· open, SecureCRT crashed.
· SecureCRT crashed if a session that specified a non-existent
· keymap was cloned or opened a second time.
· If the /NOMENU option was specified on the command line, a
· "Failed to create empty document" error was reported.
· For Ymodem transfers, 128-byte packets were sent when Ymodem-1k
· option was specified.
· The Delete, Home, End, PageUp, and PageDown keys did not work in
· the chat window.
· If the paste on middle button option was set and a middle button
· press was simulated by pressing the left and right mouse buttons
· together, the context menu was displayed.
· If the tab bar was not displayed when SecureCRT started and then
· a session was connected and the tab bar was displayed, the status
· indicator icon did not have the correct status.
· When the status indicators were shown as background colors, if
· there were more tabs than could fit across the window and a tab
· was closed, the tab bar was not redrawn correctly.
· If the toolbar was changed to a custom toolbar and then back to
· the default toolbar, the "Toolbar Options" drop-down arrow was
· no longer displayed.
· If a custom menu (.mnu) file was specified and SecureCRT was
· restarted, then the custom menu was cleared and SecureCRT was
· restarted, the toolbar icons were not displayed correctly.
· It was possible to close a locked session from the Windows 7
· taskbar.
· If SecureCRT was minimized, the live preview in the Windows 7
· taskbar displayed a busy circle until it eventually failed to
· get a thumbnail bitmap and displayed a default icon.
· If SecureCRT connected to multiple sessions at start up and then
· was minimized, the Windows 7 taskbar only contained a
· thumbnail image for one of the tabbed sessions.
October 2nd, 2009New features:
· Unicode support was improved in the following areas: character
· sets from multiple languages can be viewed in a session, display
· of right-to-left reading order languages, UTF-8 characters can
· be mapped in the Keymap Editor, Send/Receive ASCII works with
· UTF-8 data, UTF-8 filenames can be used in the SFTP tab,
· pass-through printing supports UTF-8 data, and better behavior
· with scripts that use combining marks to compose characters.
· In the Session Options dialog, the list of character encodings
· displays all the encodings supported by the system.
· Added an option that allows words to be specified in a list so
· that they can be highlighted as they appear in the session.
· An inactivity status notification option can be set for tabbed
· sessions so that activity can be monitored in tabbed sessions
· other than the current session.
· There are new display settings for tab status indicators, which
· are icons and tab background color.
· The tab bar position can be set to the bottom of the SecureCRT
· window.
· When a session is locked, a locked icon is displayed on the tab
· unless the "Color rectangles" status indicators are used.
· SecureCRT has several new Windows display themes.
· If a file is dragged from MS Explorer or other OLE-enabled
· application into a connected SecureCRT session, it can be
· transferred using ASCII, Xmodem, Ymodem, or Zmodem.
· Added a global option that allows URLs to be opened by
· CTRL+clicking them.
· A new session option allows mouse wheel scroll events to be
· sent to the remote application.
· A new script function GetActiveTab returns the currently active
· tab.
· Added the ability to wait for a case insensitive string in a
· script. The functions WaitForString and WaitForStrings take an
· optional parameter to specify that the case should be ignored.
· Additionally, the property IgnoreCase has been added to the Screen
· object so that this can be set globally.
· Added a script function SetStatusText that allows the status
· bar text to be set from a script.
· The script functions SetOption and GetOption now allow encrypted
· passwords to be used in a script.
· A command-line parameter /SESSION_FOLDER allows all the sessions
· in a folder to be connected when SecureCRT starts.
· A command-line parameter /EncryptedPassword has been added, which
· allows an encrypted password to be specified on the command line.
· SFTP: Dragging a file from MS Explorer or another OLE-enabled
· application initiates a put command on the file.
Changes:
· Increased scrolling performance when large amounts of text are
· output to the session.
· The following changes were made to the button bar: only
· configured buttons are displayed, the button width is determined
· by the button label, and the button bar menu is now on the left
· side of the bar.
· The "Semaphore timeout" error is now displayed in the session's
· trace output instead of a message box.
· The maximum value that the global maximum columns option can be
· set to is now 32,000.
· Modified the script function LogFileName so that if the log
· filename contains parameter substitutions and logging is on,
· the name of the file currently being logged to is returned.
· Added a "Start Upload" button to the Zmodem Upload List dialog.
· The character encoding restrictions on the vt100 font have been
· removed.
· In the Map Selected Key dialog, pressing the Default button
· removes the entry from the keymap file.
· In the Keymap Editor dialog, pressing ALT+O closes the dialog.
· The close button now appears on the tab itself instead of to the
· right of the tab bar.
· Serial: The baud rate is now displayed in the status bar.
Bug fixes:
· If data being sent using Send ASCII contained a null character,
· nothing after the null character was sent.
· Zmodem transfers did not complete when attempting to download
· a zero-byte file.
· The Xterm command "Use Alternate Screen Buffer" did not work.
· The anti-idle string was not sent when a session was locked.
· If a session was locked, the double-click tab action was still
· honored.
· When a session was started from the Activator, the new session
· window appeared behind other application windows.
· If a session without a username was edited while it was connected,
· the username entered during authentication was saved to the
· session.
· If multiple sessions were being edited and a port forward was
· added or deleted, only the first session was modified.
· If one tabbed session was showing the button bar and another
· tabbed session was not, then the second tab was moved to the
· first position and then back and the window was resized, the
· number of columns would increase when the mouse was released.
· The number of lines specified for the scrollback buffer of the
· first tabbed session was also used for the other tabbed sessions.
· The "Upon Disconnect" custom log data was written twice to the
· log file.
· Exiting Activator while a SecureCRT session was locked left a
· SecureCRT process running that could only be accessed through
· the Windows Task Manager.
· If the configuration folder's path had a trailing backslash,
· sessions could not be connected from the Activator or from
· SecureFX (if it was installed).
· When %I was specified as a variable in the title bar session
· option, it was not replaced with the IP address.
· If the color scheme attributes were changed while the "ANSI color"
· and "Use color scheme" options were set, the "Overstrike bold"
· attribute was not changed.
· SecureCRT had to be restarted for ANSI color table changes to take
· effect.
· The locked status of a tabbed session was not displayed correctly
· in the status bar until the mouse moved over the toolbar or menu
· bar, or the mouse was clicked in the session window.
· If a window other than SecureCRT had focus and Connect was
· called from a script, the SecureCRT window could get focus.
· If the active tabbed session was disconnected, text could not
· be pasted into the chat window.
· If the installer was run in silent mode and an answer file that
· could not be found was specified on the command line, a dialog
· was displayed.
· SecureCRT offered to make itself the default Telnet handler even
· when the Telnet protocol DLL was not available.
· RLogin: Sending window size messages to the server when they had
· not been requested could cause garbage to be displayed in the
· session.
· Serial, TAPI: Zmodem transfers over Serial or TAPI did not switch
· into and out of binary mode correctly, which could cause the
· transfers to hang or transfer the same file repeatedly.
· Serial: When a button was mapped to send a string of non-printing
· octal characters, the order of the characters was sometimes
· swapped when they were sent.
· SSH1/SSH2: In the Enter SSH Username dialog, if the Save
· username check box was checked and the Auto Save Settings
· option was off, the username was not saved.
· SSH2: In the Key Generation wizard, if the specified path for the
· key contained two or more folders that did not exist, they key
· could not be saved.
September 11th, 2009Changes:
· SecureCRT uses the Microsoft developer libraries that contain the 07/28/2009 ATL update.
· The global value for the maximum number of columns can be set to a value as small as 132.
Bug fixes:
· SecureCRT 6.2.2 could get into a state where it attempted to connect to a session that did not exist, which caused a crash.
· If a custom .mnu file that contained a syntax error was specified, it could cause multiple SecureCRT.exe processes to be started and then SecureCRT crashed.
· If text was being output and the session was scrolled up using the mouse wheel, text selected using the mouse was not selected correctly.
· In version 6.2.2, if a session that used ANSI colors and the color scheme was modified so that it no longer used the color scheme, the session display was not refreshed.
· TAPI: Phone numbers could not be saved for TAPI sessions.
July 2nd, 2009Changes:
· Added support for administratively prohibiting checking for updates from within SecureCRT
Bug fixes:
· SecureCRT could crash if a session showing elapsed time was connected and the Windows system date or time was set to a value in the past
· If a session that required a password was cloned, the password had to be entered again
· When the session option "Use Windows copy and paste hotkeys" was set, the hotkeys for Find and Select All did not work
· If the path in the "Select File to Send as ASCII" dialog was changed, it was not remembered the next time that dialog was displayed. It is now remembered until SecureCRT exits
· The installer did not honor LICENSE_FILE or CONFIG_FOLDER_PATH entries that were specified in an ANSWERFILE
· Silent installs did not add the program to the Start menu or the list of installed programs in the Windows Control Panel
· Telnet: If a logon script that did not send an initial carriage return was specified for a session, a carriage return (OxOD) was sent in a separate packet during authentication, which caused authentication to fail if the server used line mode
· SSH2: Previously, the default GEX preferred key size was changed from 2046 to 2048. However, the GSSAPI GEX maximum key size was still 2046, which caused the server to report an error and disconnect the session when GSSAPI GEX was used
April 29th, 2009· SecureCRT could not be installed on systems where InstallShield custom actions do not work.
· If a license with a maintenance date in the format MM-DD-YY was entered, SecureCRT crashed.
· Under Vista, the mouse wheel did not scroll if the system used the MS Explorer Mouse driver.
· Function and arrow keys did not work correctly with servers that expect all the characters in escape sequences to be sent in the same packet.
· In a session with the "Retain size and font" option set, if the window was resized so that it was smaller than the logical rows and columns, the wrong text was highlighted during a find operation.
· If a session was opened in a new window and the window was closed prior to authentication completing, authentication prompts continued to be displayed.
· In the Keymap Editor, if a key was selected and a keymap that mapped that key was loaded, the keymap assignment display was not updated.
· In the Connect dialog, a session that was copied could not be pasted more than two times.
· If the Visual Studio 2008 DLLs were not in the side-by-side cache, MFC90.DLL errors were written to the event viewer when SecureCRT ran.
· SSH1/SSH2: If an RSA key with a passphrase was added in the
· Manage Agent Keys dialog and the wrong passphrase was entered, the incorrect error "The key packet is corrupt, damaged, or incompatibly formatted" was reported and was still reported after the correct passphrase was entered.
March 19th, 2009· SecureCRT crashed if a session was disconnected before the shell
· request succeeded.
· SecureCRT crashed if the File menu was selected after the menu
· bar was reset to Default from the Menus tab in the Customize
· menu.
· When some escaped ASCII characters such as "200" were sent
· to the remote system from a script or a mapped key, they
· were transformed first.
· With the "Retain size and font" option set, the PageUp and
· PageDown keys scrolled a different amount than when using the
· mouse to page up and page down.
· The trace output displayed garbage for an "Unknown
· CHANNEL_REQUEST" message.
· When generating a public key in the Key Generation wizard, the
· progress bar was not displayed until after the key had been
· generated.
· Three-year licenses were not being honored.
· In the Connect dialog, when a new folder was added, a folder
· called "New Folder" was also added.
· In the Connect dialog, attempting to rename a session to the same
· name as its parent folder reported an error that the name was
· already in use.
· After pasting a copied session into a folder in the Connect
· dialog, the folder was selected.
· SSH1: When SecureCRT was installed on a U3 drive, public-key
· authentication always failed for SSH1 sessions.
· SSH2: Attempting to authenticate using GSSAPI with the 64-bit
· MIT Kerberos DLL failed.
· SFTP: If a transfer operation was cancelled using CTRL+C, the
· SFTP tab became unresponsive.
February 24th, 2009Bug fixes:
· If a custom menu file that contained MENU_SCRIPT_MRU_FILE1 was
· used, selecting a script from the recently used script list could
· launch the wrong script.
· If the "User Arranged Tree" option was set in the Connect dialog
· and sessions were rearranged, the changes were not saved.
· If two sessions had different color schemes and a session was
· sent to a new window, and then a session was dragged into the
· other window, it had the first tabbed session's color scheme.
· Selecting "Print Setup" from the File menu always displayed the
· printer settings for the first tabbed session.
· RLogin: RLogin sessions could disconnect after a large amount of
· data was received.
· SSH1/SSH2: An X11 forwarding request succeeded when it should have
· failed because a different user connected.
February 18th, 2009Bug fixes:
· Under Vista, selecting a file using "Zmodem Upload List..." from
· the Transfer menu caused SecureCRT to crash.
· If the "Clear on disconnect" option was set and SecureCRT went
· into full screen mode after disconnecting from a session that
· had more than a page of output, SecureCRT crashed.
· SecureCRT could crash after attempting to connect to a host that
· was not responding.
· Under certain circumstances, SecureCRT could crash after
· scrolling back and then attempting to select some text.
· If a session setting was changed in the Session Options dialog
· and then the Session Options dialog was re-opened, SecureCRT
· sometimes crashed.
· If the X/Y/Zmodem upload and download folders did not exist and
· a Zmodem download was started and the "Browse for Folder" dialog
· was used after the transfer had timed out, SecureCRT crashed.
· If the command line specified a path for a script, the script
· was not launched.
· On a 64-bit machine, Help could not be launched.
· With the "Retain size and font" option set, under certain
· circumstances, data displayed in the session window could not
· be selected.
· If a Zmodem transfer was started and the download directory was
· not valid, if the "Browse for Folder" dialog was cancelled after
· the transfer timed out, garbage characters were sent to the
· server.
· In the Connect dialog, if several sessions were selected and one
· was de-selected, when the mouse was right-clicked to display the
· context menu, the session was selected.
· New color schemes added to an active session were not saved to
· the configuration file.
· The 64-bit combined SecureCRT and SecureFX installer installed
· into the x86 location when run in silent mode.
· In the installer, on the dialog that shows where the
· application is going to be installed, long install location
· paths were cut off.
· The upgrade eligibility date displayed in the installer was not
· correct.
January 30th, 2009New features:
· A native 64-bit Windows version is available.
· Multiple sessions can be selected and edited from the Connect
· dialog. Only the changed fields will be applied to the
· selected sessions, which allows specific settings to be
· changed for a group of sessions.
· There is a new option to remember which sessions were open the
· last time SecureCRT ran so that they can be launched the next
· time the application runs.
· Added an option to create a new log file at midnight, which
· can be used to do automatic log rotation.
· Added support for creating folders when a log file path is
· specified that does not already exist, which allows parameter
· substitutions to be used in folder names for log file paths.
· Added a command-line parameter /LOG, which allows a log file to
· be specified on the command line.
· A blank password can be used to lock a session, which makes it
· easier to prevent accidental typing in sessions.
· SSH2: Added support for PKCS#11, allowing a Cryptographic Token
· Interface to be used for smart-card authentication.
· SSH2: In the Activator, agent support has been enhanced by
· allowing keys to be explicitly added and removed.
· SFTP: Added support for recursive remove (rm -r).
· SFTP: Added support for the flags -a and -d to the ls and lls
· commands.
Changes:
· Empty cells are not stored in the scrollback buffer, which in
· most cases, significantly reduces the amount of memory used by
· a session.
· The default Maximum columns setting has been increased to 256.
· The default download, upload, and public key generation folders
· have been changed to "My Documents". Under Vista, the default
· download folder is the user's Download folder. Only new
· installations are affected.
· When SecureCRT and SecureFX are integrated, if the SecureFX
· button on the SecureCRT toolbar is pressed and the current
· session does not have a valid file transfer protocol
· specified, a more informative message is displayed.
· Serial: Added support for changing the baud rate of a connected
· session.
· SSH1/SSH2: Added support for specifying a password in the
· Session Options dialog.
· SSH1/SSH2: When creating an identity file, moving the mouse is
· no longer required to generate random data.
Bug fixes:
· A script that called crt.Close immediately after calling
· crt.Screen.Send could cause SecureCRT to crash.
· Connecting multiple sessions in tabs from a script sometimes did
· not work correctly and some sessions hung or did not connect.
· If the first tabbed session used the vt100 font, a session
· that used UTF-8 encoding could not be cloned.
· The terminal dimensions were not updated when tabs were dragged
· between windows of different dimensions.
· After exiting a session of vi that changed the foreground and
· background colors, the foreground and background colors were not
· restored correctly.
· In some cases, the scrollbar was in the wrong position after
· switching between tabbed sessions.
· When downloading a file that contained an illegal character
· such as ":" using Zmodem or Ymodem, the file name was truncated
· at the illegal character. Illegal characters are now replaced
· with "_".
· If a firewall was specified on the command line and the firewall
· name contained a space, it was not used.
· If the "Auto Save Options" setting was off and a value was
· changed in the Global Options dialog, if the Global Options
· dialog was re-opened, the change was not reflected in the
· dialog.
· SecureCRT had to be restarted in order for changes made to the
· Default session to be honored in Quick Connect.
· If a session was deleted while it was connected, the session was
· added to the session database after it was disconnected.
· If the "Retain size and font" option was set and the window was
· resized, under certain circumstances, some lines did not have
· the correct background color.
· If a firewall failed to connect and the "Auto reconnect" option
· was set, a new firewall authentication dialog was displayed
· every second.
December 3rd, 2008· CRT could crash if the "Auto reconnect" option was set and
· the username was changed when attempting to connect to a
· server that does not allow the username to change.
· If the INI-file-only global option "Disable Close" was set and
· CRT was closed using the red "X", CRT hung.
· If a script was specified on the command line and the "Show
· connect dialog on startup" option was set, the Connect dialog
· was displayed.
· If there was an error during script recording and the error
· message was longer than 64K, the message could not be displayed.
November 7th, 2008Changes:
· SSH2: In the session .INI file, if the GEX Preferred Size was set to 2046, it will be changed to 2048 in order to be compatible with Cisco IOS 12.4 or later.
Bug fixes:
· If a script was specified on the command line, SecureCRT was in a hung state after the script executed.
· With ANSI color enabled, if a color escape sequence was received, only the portion of the row that contained characters was correctly displayed.
· SSH2: In an SFTP tab, if the connection was lost and a put command was issued, SecureCRT crashed.
October 3rd, 2008· - If the auto-reconnect option was set for a session and the
· connection was lost, an error dialog was displayed. The 5.5
· behavior of not displaying a dialog was restored.
· - If the session option "Display logon prompts in terminal window"
· was not set and a logon script was specified, the script was
· started before the connection was established. The 6.0 behavior
· of starting the script after the connection is established was
· restored.
· - Logon scripts were run when the administrative option to disallow
· scripts from being run in SecureCRT was set.
· - If the global option "Show confirm disconnect dialog" was set and
· multiple sessions were open in different windows, exiting the
· Activator could cause SecureCRT to crash.
· - SecureCRT crashed when cancelling out of the select log file
· dialog if the session tab no longer existed.
· - In the Connect dialog, doing a Find Next after deleting a session
· that had been found using Find caused SecureCRT to crash.
· - In the Global Options dialog, on the Firewall page, double-
· clicking the empty space below the firewall list or pressing the
· DEL key when no firewall was selected caused SecureCRT to crash.
· - After answering "No" to the confirm disconnect dialog, SecureCRT
· became unresponsive.
· - Under certain circumstances, if there were multiple SecureCRT
· windows and the menu bar was toggled, SecureCRT could become
· unresponsive.
· - After selecting text in the scrollback buffer using a triple-
· click, it was no longer possible to select text in the scrollback
· buffer.
· - If the SecureCRT window was maximized after scrolling up, garbage
· was displayed in the session window.
· - If an "exit" command was sent to a session in a script and then
· another connection was immediately attempted, it could cause the
· script to hang.
· - If a session was connected using the Session.Connect(/s )
· scripting method, the initial position specified in the session
· options was not honored.
· - SSH2: The TCP connection associated with a dynamic port forward
· could get stuck in a CLOSE_WAIT state after the session was
· disconnected.
· - SSH2: Under certain circumstances, dynamic port forwarding was not
· started when a session was connected.
· - SSH1/SSH2: If the session option "Start log upon connect" was set
· and no log file was specified, when connecting to the session,
· after entering the password, focus went to the session window
· instead of the Select Log File dialog.
· - Global Secure Shell configuration information was not being
· migrated.
· - If two sessions had the same name, hostname, and username, they
· were combined during migration, but only the terminal protocol
· was set.
August 22nd, 2008· Under certain circumstances, SecureCRT could not write log files to a mapped drive.
· Under certain circumstances, when Quick Connect was used to make multiple connections, the authentication dialog was associated with the initial session window.
· If nothing had previously been typed into the session window, pressing ALT sent the number to the session rather than switching to the specified tab.
· When Windows was configured to use large fonts (120 DPI), some text in the Session Options dialog did not fit in the dialog.
· If a URL that spanned multiple lines had extra spaces at the end of a line, the extra spaces were not removed when the URL was opened.
· Serial: After a serial session was disconnected, the tab connection status indicator was not updated to reflect that the session had been disconnected
July 31st, 2008· SSH2: Because of a limitation in some recent versions of Cisco's IOS which resulted in SecureCRT not being able to connect, the diffie-hellman-group-exchange key exchange algorithm was modified to send a different maximum size for the modulus.
· SecureCRT crashed when running a script that attempted to connect to multiple sessions.
· Calling Config.GetOption("Password") in a script caused SecureCRT to crash.
· After calling the script Session object method Connect, execution of the script continued regardless of whether or not authentication had completed.
· When the global option "CTRL TAB switches to most recently used tab" was set, pressing CTRL TAB cycled between all the tabs rather than going to the most recently used tab.
· Under certain circumstances, launching SecureCRT caused MFC80U.dll errors to be reported in the Windows Event Viewer.
· Serial: After sending CTRL C to a serial device, SecureCRT hung.
July 25th, 2008· The active toolbar theme was not saved when SecureCRT was closed and restarted.
· The status bar always used the "Office 2000" theme regardless of the currently selected theme.
· If a custom menu (.MNU) file specified a system menu, the system enu reverted to the default menu after a session was connected.
· The installer did not handle the answer file option
· INSTALLATION_PROFILE.
· If FIPS mode was enabled and an SSH1 session was specified as an auto session, SecureCRT crashed.
July 18th, 2008· Under Windows 2000, a KERNEL32.dll error was reported when SecureCRT started.
· SecureCRT crashed when the Script menu option was selected if the Recent Script list contained at least six items.
· Leading spaces were removed when copied from the terminal window to the clipboard.
· When a second session was started in a new maximized window, the logon prompt was displayed part way down the screen.
· Under certain circumstances, if SecureCRT was started and then maximized, the logon prompt was not visible.
· When custom log data was specified, long lines were wrapped in the log file.
· If a session was reconnected while minimized and then it was restored, the size would be different.
· The Activator used a different configuration folder than SecureCRT when SecureCRT specified the /F command-line option.
· When the custom menu (.MNU) option MENU_TAB_LIST1 was used, the menu did not display the list of tabbed sessions.
· RLogin: SecureCRT could crash when an RLogin session wasdisconnected.
· TAPI: SecureCRT crashed when the remote host was VMS and thesession was disconnected by logging off the host machine.
July 3rd, 2008· If SecureCRT was running during an upgrade install, the installer continued to report that a file was in use after SecureCRT was closed and Retry was selected.
· The installer did not handle the answer file option INSTALLATION_PROFILE.
· SSH1: If a command that resulted in a lot of output was run,
· pressing CTRL C could cause the session to become unresponsive.
June 20th, 2008New features:
· Added the ability to search sessions and folders in the Connect
· dialog, which supports searching for a session name, hostname,
· folder name, or a keyword in the description.
· Added items to the File menu to reconnect all disconnected
· sessions and disconnect all connected sessions.
· Added support for an unlimited number of automated logon
· Expect/Send sequences and the ability to delete and reorder
· the sequences.
· Several example VB scripts are installed, which demonstrate how
· to use SecureCRT's scripting support.
· Added scripting support for sending special keys such as
· function keys, control keys, and other special characters,
· which makes it easier to write scripts that are protocol
· and emulation independent.
· Added Clipboard scripting functions provide access to the
· current selected text and also to available Clipboard data,
· which allows setting up actions such as running a script
· that uses the contents of the Clipboard to send a command
· to the session, or selecting text in the session and running
· a script which launches a web browser to google that text.
· Added scripting support for accessing session options, which
· makes it possible to do operations such as configuring a session
· before connecting and converting session information stored in a
· file to saved sessions.
· Added error handling methods to the Application scripting
· object. The new methods GetLastError and GetLastErrorMessage
· provide flexibility to how errors are handled in scripts.
· The script method Connect can be called without arguments in
· order to reconnect a session.
· SSH1/SSH2: Added an option for authentication credentials to be
· entered in the terminal window, which allows Secure Shell logons
· to be scripted using the Expect/Send strings or "Logon script"
· option found in the Session Options dialog.
· SSH1/SSH2: The username and password can be saved when using
· keyboard-interactive authentication, streamlining the logon
· process.
· SSH1/SSH2: Added a session option to execute a remote command
· after connecting.
· SFTP: Added a "view" command which downloads the specified file
· and opens it in the default editor or appropriate application.
· SFTP: If the remote server is VShell 3.5 or later, there is a
· "su" command in the SFTP tab that allows you to become a
· different user.
Changes:
· When the "Single Instance" and "Launch New Windows in a
· Separate Process" options are set, sessions cannot be opened in
· a separate window.
· The serial port can now be changed in the Default session.
· Added read access to the crt.FileTransfer.ZmodemUploadAscii
· property.
· SSH2: The option "Enable OpenSSH agent forwarding" can be
· specified on a per-session basis.
Bug fixes:
· When the session option "Retain size and font" was set, if
· the window was resized to be smaller than the number of
· logical rows, it was not possible to scroll to the rows that
· were cut off.
· If a session was maximized and the "Synchronize view to size"
· option was set, if the session was sent to a new window, the
· logical rows and columns in the new window were incorrect.
· Unicode output was not displayed correctly in a tabbed session
· other than the first tab.
· Under certain circumstances with SecureCRT maximized, text
· could be cut off when switching between tabbed sessions.
· Opening a new window while in full screen mode caused the new
· window to appear partially off screen.
· Under certain circumstances, a second SecureCRT window for an
· existing session was cascaded when it shouldn't have been.
· If two sessions with different initial positions were connected,
· only the initial position for the first session was honored.
· If the "Auto reconnect" option was set and authentication was
· cancelled by the user, the session attempted to auto reconnect.
· Under certain circumstances when the "Auto reconnect" option
· was enabled, a session attempted to reconnect even though its
· associated tab had been closed.
· When the "Save expanded folder state in connect dialog" option
· was set and a session in a folder was renamed in the Connect
· dialog, it caused other folders to be expanded.
· It was not possible to map a key or button to "Trace Options"
· or "Raw Log Session".
· The recent scripts menu item MENU_SCRIPT_MRU_FILE1 did not work
· when used in a custom .MNU file.
· In a script, certain crt.Screen.ReadString syntax errors could
· result in a crash.
· In a script, if a Connect call was made immediately after a
· Disconnect call, SecureCRT could think the session was not
· connected.
· Under certain circumstances, the line number reported when a
· script was cancelled was incorrect.
· Paste output did not continue if a WaitForStrings script method
· matched something in the pasted text.
· SSH2: SecureCRT could crash when web traffic was forwarded
· through Firefox's Foxy-Proxy.
· SSH2: When a certificate from a CAPI store was used to
· authenticate, agent forwarding did not work.
· SFTP: On some platforms, such as rhel5 and rhel4-64, wildcard
· (ls -l *) file listings were returned in the wrong order.
· U3: Configuration settings were uninstalled when the U3 version
· was uninstalled.
April 25th, 2008Changes:
· Dot files, such as ".svn", that are in the configuration folder no longer displayed in the Connect dialog.
· When the administrative option to disable all scripting is on,
· scripts cannot be recorded.
· Added the global .INI-file-only option "Focus Does Not Affect Blink" that allows text with the blinking attribute set to blink when the SecureCRT window does not have focus.
· SSH2: The "Enable OpenSSH agent forwarding" option is now off by default. This only affects new installations.
Bug fixes:
· When there was a single tab, sending that tab to a new window multiple times could cause SecureCRT to crash.
· Under certain circumstances, attempting to modify a session with a logon script could cause SecureCRT to crash.
· If the File menu was opened and there was not enough room for it to be displayed, SecureCRT crashed.
· If the context menu was displayed for an inactive tab with the "Close on disconnect" option set and the tab was disconnected while the menu was displayed, selecting a menu item other than
· "Close" caused SecureCRT to crash.
· The status bar was being updated more than necessary, which increased CPU usage.
· Under certain circumstances, sessions that were disconnected could not be reconnected.
· Pressing CTRL SHIFT V did not perform a paste operation.
· After using Print Setup to select a different printer, printing
· no longer worked.
· The option not to display the "Check for Updates" dialog was
· only saved if the "Auto Save Options" option was set.
· In a script, if a disconnected tab was reconnected, it was
· connected in a new tab.
· In a script, the ConnectInTab method did not honor the "On Error Resume Next" statement.
· If SecureCRT and SecureFX were installed separately, but used the
· same configuration folder, when a session was created or modified, the protocol for the other application was set to None.
· Accelerator keys defined in custom menu .MNU files were not
· being honored.
· If a custom menu .MNU file contained more than 1000 items, it
· could not be loaded.
· Under certain circumstances, the installer incorrectly reported
· a "file in use" error, which prevented the application from
· being installed.
· Silent installs that specified an ANSWERFILE containing a
· parameter substitution did not work.
· Under Vista, if an MSI installer was used, the default
· installation folder was in "Application Data" instead of
· "Program Files".
· Telnet: If a session was saved in the maximized state, the rows
· and columns were not set correctly on the host the next time it
· was connected.
· SSH2: If a proxy such as Proxycap or Foxy-Proxy was being used,
· SecureCRT crashed when attempting to connect a session that did
· port forwarding.
· SSH2: SecureCRT could crash if a session was closed while
· attempting to port forward to a destination that was not
· listening or a host that did not resolve.
February 21st, 2008· Updated the View menu to show that ALT ENTER is the keyboard accelerator for Full Screen.
· SecureCRT crashed when a button configured to run a script that no longer existed was pressed and SecureCRT attempted to remove that script from the recently used script list.
· When extended ASCII characters (0x80-0xFF) were used as word delimiters, SecureCRT crashed.
· If the script function crt.Window.Show was called and then the session was connected, SecureCRT crashed.
· Under certain circumstances, the window got progressively smaller when switching between 80 and 132 columns.
· When reverse video text was printed, there were lines between the letters.
· Under certain circumstances, underline characters were not printed.
· SecureCRT could no longer connect to a session through a Humming-bird SOCKS firewall.
· A simulated middle mouse-button click from a mouse with two buttons no longer worked.
· The help text for menu and toolbar items was not being displayed in the status bar.
· File dialogs, such as the Zmodem dialog, could not be resized.
· The /NOTOOLBAR and /NOMENU command-line options no longer worked.
· When a custom menu file was used, selections that existed in a sub-menu within the context menu did not execute.
· When a custom menu .MNU file was specified and the .MNU file was changed, the changes were not honored.
· When used with a U3 smart drive, valid license data was not saved if the first attempt to enter the license had invalid data.
· RLogin: The rows and columns were not set on connect.
· SSH2: When an attempt to upload a public key from the Quick Connect dialog was made and the hostname had not been specified, SecureCRT crashed.
· SSH2: After changing the password on an OpenSSH 3.6 server, SecureCRT crashed when attempting to logon.
January 8th, 2008· SecureCRT could crash if a session was disconnected while a script was in the WaitForStrings function.
· The WaitForStrings script function incorrectly matched the shortest string instead of the longest string.
· If an auto session contained multiple sessions and the check for updates dialog was displayed on startup, only the first session connected.
· When the substitution parameter %h was specified in a log file name, GMT rather than local time was used.
· After clicking on an inactive disconnected tabbed session, the mouse pointer disappeared until the mouse was moved.
· When the tab context menu was used to disconnect a session, the tab status indicator was not correctly updated.
· The mnemonic for "Clear Screen and Scrollback" on the Edit menu did not work.
· File browser dialogs could not be resized.
· SSH2: When the path for the identity file contained an environment variable, the Public Key Properties dialog could not display the fingerprint, upload the key, or change the passphrase.
· SSH2: In the Public Key Properties dialog, if the key file path was blank, it was filled in after cancelling out of the file browser.
December 19th, 2007· In some cases, when third-party firewall software was installed, sessions could not connect.
· When MENU_WINDOW_NEXT was called from a mapped key or button or from a custom .MNU file, SecureCRT crashed.
· SecureCRT sometimes crashed when doing pass-through printing.
· When the Activator was used to connect a folder of sessions, not all sessions in the folder were connected.
· The Recently Used Session List wasn't updated when a session was selected from the Activator.
· The UNIX/Linux "resize" command did not work because it could not get the rows and columns.
· If a session was connected and a session with a different number of rows and columns was launched in a new window, it had the same number of rows and columns as the first session.
· After running a script that displayed a message box, focus was not returned to the session window.
· If an SFTP tab was sent or dragged to another window, an extra "SFTP-" was prepended to the tab title.
· Telnet/RLogin: Read requests were queued and attempts to process data were made when the session was not connected, which resulted in a WSAENOTCONNECTED error.
· Telnet: Zmodem transfers were significantly slower in version 6.0 than in previous versions.
December 7th, 2007· The installer no longer requires a reboot upon completion.
· The U3 installer is now packaged as a .exe instead of a .u3p. This prevents it from being downloaded as a .zip.
· Quick Connect did not work when the "Save session" check box was unchecked.
· When the logon Expect and Send strings contained the "%" character, SecureCRT attempted to do a variable expansion, which caused the logon to fail.
· Saved passwords were not used when the "Auto Save Options" setting was off.
· Inserting a CTRL ENTER in the Send string in a button configuration caused the button to lose its configuration when SecureCRT restarted.
· When the global option "Only show tabs when there are more than one" was set and a session was dragged to a window that only had one session, the tabs were not shown.
· Under certain circumstances, selecting a tab could cause it to move unexpectedly to a different position.
· Under certain circumstances, when using Quick Connect, the password prompt appeared in the wrong window.
· When a recently used script or session path was too long to fit in the menu, the path was truncated before the script or session name.
· Telnet and Telnet/SSL: After pressing CTRL ENTER when output was scrolling, it could take a long time for the output to stop.
· SSH2: When using keyboard-interactive authentication, if an error dialog appeared after the password prompt, SecureCRT crashed.
November 27th, 2007· The U3 installer installs the history and readme files in the Exec folder.
· The U3 installer installs the sample scripts, menus, and keymaps in the DataExamples folder.
· Changing the font of a tabbed session could cause SecureCRT to crash.
· SecureCRT crashed when attempting to enter license data after making changes in the Global Options dialog.
· SecureCRT failed to start if the default session's protocol was Serial or TAPI.
· The session tab was blank when the session used the vt100 font and the tab title was set with an escape sequence.
· If a tab title was set using the titlebar escape sequence and the session was sent or dragged to another window, the tab title reverted to the session name.
· Keyboard input was not correct with certain fonts, such as Cyrillic, that used UTF-8 character encoding.
· Text could be pasted into a locked session.
· The "Autosave Options" setting was always set to true when SecureCRT started.
· If the global option "Save window state for each session" was set and a new session was created and connected and then connected in a new window, the number of rows was incorrect.
· When the remote host rejected the connection, SecureCRT incorrectly reported the error "The specified network name is no longer available".
· SSH2: SecureCRT crashed on exit when using an SSH2 session with three or more port forwards over an SSH2 SOCKS firewall.
· The amount of disk space the U3 installer checked for was much larger than necessary.
· The U3 version was looking on the hard drive for the menu and toolbar XML file.
November 16th, 2007· Added support for sending a tabbed session to a new window and cloning a session in a new window. Sessions can also be dragged between SecureCRT windows.
· Added an optional button bar that allows buttons to be mapped to strings, protocol functions, menu commands, scripts, etc. Different button bars can be created so that they can be used on a per session or per task basis.
· Added support for launching external programs on the local machine through mapped keys and buttons on the button bar.
· Added support for alpha transparency. The transparency can be set for the active and inactive windows. This allows viewing of items behind the SecureCRT window and the contents of two SecureCRT windows to be compared.
· Added support for several Windows themes, which give the user interface a more modern appearance.
· Added support for customizing the toolbar and menu by dragging and dropping items while in the Customize dialog.
· Added a new default color scheme, "White / Black", which is a white foreground on a black background.
· Enhanced portability by making a U3 installer available. Installing SecureCRT on a U3 drive makes it easier to use on any machine.
· Added MSI installer support.
· Added optional monthly pop-up dialog that offers to check for product updates.
· Added support for locking sessions with a password while connected. While a session is locked, it cannot be typed in or closed.
· Environment variables can be used in all paths specified in global and session options, which allows configuration files to be used by more than one person and makes it easier to move configuration files to other machines.
· The autoreconnect prompt and countdown are now displayed in the session window instead of in a dialog. This allows connected sessions to be used while a disconnected session is trying to reconnect.
· Added support for the Ymodem file transfer protocol.
· Added "Connect to multiple sessions sequentially" to the TerminalAdvanced page in the Global Options dialog. When this option is set and multiple sessions are connecting, they will connect one after the other instead of at the same time.
· Added a global option not to reuse disconnected tabs for connecting new sessions.
· Extended the command-line options to support a username@hostname format.
· Added new Session script object function LogUsingSessionOptions that uses the specified session's logging options.
· Telnet: Added a session option to enable/disable NTLM authentication.
· SSH2: Added a command-line option to specify the compression type(s).
· The standard toolbar icons have been updated to use Windows Vista icons.
· SecureCRT dialogs now use the font specified by the Windows display properties.
· The line and character send delay settings, which were global settings, are now session-specific settings.
· The scrollback buffer can be set to be up to 128,000 lines.
· If the logging option "Append to file" is set and the session .INI file option "Log Multiple Sessions" is off, when one session is already logging to a file and another session tries to log to the same file, the user will be prompted for a different log file.
· When recording a script, crt.Screen.Synchronous is set to true by default. This prevents data being lost by the script sending data too fast to be transmitted to the remote system.
· If a script that does not exist is selected from the recently used script list, a prompt asking if it should be removed from the list is displayed.
· The "Save password" check box is no longer shown on the "Enter Password" dialog when the "Auto Save Options" setting is off.
· The global settings "Copy on Select" and "Paste on right button" are on by default. This only affects new installations.
· Pressing the " " key on the numpad now produces a " " character in Linux and ANSI emulations.
· Improved the error message that is displayed when attempting to give a session a name that is already being used.
· Fixed: SecureCRT could crash when applying default session changes to all sessions.
· Fixed: Files with Unicode names may not have been named correctly when transferred using Zmodem.
· Fixed: Pasting into a SecureCRT session from an RDP session caused SecureCRT to hang.
· Fixed: When using TrueType or ClearType fonts in a session, the right edge of some characters was cut off.
· Fixed: If the session options "ANSI Color" and "Use Color Scheme" were enabled for the first tab, if a second tab was connected, the background color was not correct.
· Fixed: The command-line option /POS did not override the session's initial position.
· Fixed: If a relative path was specified for a custom menu that contained a script path and a log file that was in a different location than the script was used, the script could not be found.
· Fixed: Xmodem transfers could fail when the remote machine sent a NAK. SecureCRT now handles the NAK.
· Fixed: Unicode characters were not displayed correctly in the title bar.
· Fixed: When the SecureCRT window was as tall as the monitor and then the chat window was shown, text in the session was obscured.
· Fixed: Some menu item labels, such as Copy and About, could not be customized.
· Fixed: DOS device names such as CON, NUL, PRN, COM1, COM2, etc. could be used as session names.
· Fixed: SSH1/SSH2: When a password was specified in a URL session, it was not used.
· Fixed: Telnet/SSL: Connecting to a server that was using a certificate with a large key size, could have resulted in the following error: "The buffers supplied to a function was too small".
· Fixed: SFTP tab downloads failed if the file contained any characters that were illegal on the local file system (i.e., / : * ? " < > | ). SecureCRT now replaces any illegal characters with an underscore during the download.
August 15th, 2007· Under Vista, the default upload and download folders are in the Application Data folder instead of the SecureCRT install folder.
· SecureCRT could crash if the session was disconnected while a script was running.
· When SecureCRT and SecureFX were integrated, changing the terminal protocol from None to something else could cause SecureCRT to crash.
· When the session option "Enable Keypad Mode Switching" was off, escape sequences that switched the keypad mode were not ignored.
· When /T was specified on the command line, the command line was truncated.
· IPv6 addresses were displayed incorrectly in log and trace output.
· Under Vista, the Connect dialog did not allow multiple sessions to be selected using CTRL click.
· Under Vista, when "Open URL" was selected, the link did not work if it did not contain "http://" at the beginning.
· In the installer, text was cut off on the install success dialog when large DPI was enabled in the system Display Properties.
· In FIPS mode, creating OpenSSH format keys and converting private keys to OpenSSH format failed.
· SSH2: SecureCRT crashed when attempting to import a host key.
· SFTP: In the SFTP tab, commands that require remote paths did not work with IBM 4690 and MultiNet 5.1 servers.
May 18th, 2007· The Activator no longer worked when launched directly (e.g., from a desktop shortcut).
· The cursor was always placed in the main window when SecureCRT regained focus, even if the cursor had been in the chat window.
· SSH2: SecureCRT crashed when attempting to convert an SSH1 key pair to OpenSSH format. Only SSH2 key pairs can be converted.
· SSH2: When converting an SSH key to OpenSSH format, if the filename for the converted key was not changed and "No" was selected at the overwrite prompt, it was not possible to enter a new name.
April 5th, 2007· SSH2: The SSH_IGNORE message is only shown in trace output when the session's trace level is set to a value greater than one.
October 23rd, 2006· New tab enhancements: Launching new tabs (With this new command-line option, you can launch new sessions in tabs in the current window), Scripting tabs (Working with tabs in scripts is supported through functions that allow scripts to connect tabs, clone tabs, activate tabs, and close tabs), CTRL TAB (You can now set an option to have CTRL TAB switch to the most recently used tab), Tooltips (Hover text for tab labels lets you see the full session name when the session name does not fit on the tab display)
· Improved HTTP proxy support. Proxy setup is simplified with support for unauthenticated and basic HTTP proxies.
· Display elapsed time. Know how long you've been connected by using the option to display the elapsed time in the status bar.
· Paste on right mouse click. Quickly paste text into a session by using the option to paste on a right mouse click.
July 26th, 2006· SSH1: Compression is now off by default.
· Reduced the time it takes for the Connect dialog to display, which was noticeable on a network or USB drive.
· Running a script that modified the ANSI colors caused SecureCRT to crash.
· When CTRL TAB was used to switch between tabs, the scrollbar had the position of the most recently active tab rather than the previous position for that tab.
· The keymap assignments changed when there were multiple tabs and a session in a tab other than the first tab was reset.
· It was not possible to specify a UNC path (Samba) for a log file as it was in versions prior to 5.0.
· In SecureCRT 5.1.2, it was not possible to disable "Send initial carriage return" in Logon Scripts as in previous versions.
· Upgrading to a newer version of SecureCRT did not remove the old entry in Add/Remove programs.
· SSH1: Under certain circumstances, SSH1 port forwarding ended abruptly.
· SSH1: When generating an RSA key for an SSH1 session, if the user did not have write permissions for the specified save folder, SecureCRT crashed.
· SSH1: The NO-OP anti-idle option caused random characters to be sent to Cisco ISR routers. The "Send protocol NO-OP" session option can now be turned off for SSH1 sessions.
· SSH1: It was not possible to specify the DES cipher from the command line for SSH1 sessions.
· VSFTP: If the "version" command was issued when VSFTP was not connected to a session, VSFTP crashed
July 3rd, 2006· Line drawing did not work correctly for SCO ANSI emulation.
· When the default session was edited and a tab other than the first tab was active, the "Apply change to all sessions?" prompt was displayed even if no changes were made.
· Under certain circumstances, the color change sequence for 256-color Xterm emulation was split between buffers, which caused some colors to be displayed incorrectly.
· SSH2: SecureCRT could crash when using the TAB key to complete a filename in an SFTP tab, especially if TAB was pressed multiple
Find us on Google+
