Thursday, October 02, 2008
SecureCRT + SecureFX 6.1.1
http://www.cnbeta.com/articles/66155.htm
--------------------------------------------------------
Bug fixes:
- 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.
SecureCRT 是高度可定制的终端仿真器,适用于 Internet 和Intranet.
支持 IPv6 标准.对于连接到运行 Windows、UNIX 和 VMS 的远程系统来说,SecureCRT 是理想的选择.
下载:SecureCRT 6.1.1下载:SecureFX 6.1.1
--------------------------------------------------------
Bug fixes:
- 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.
Labels: 终端仿真器
