SecureCRT ще ви помогне да осъществите криптирана връзка със отдалечени сървъри и устройства, използвайки Secure Shell (SSH1 and SSH2) сесии. Програмата разполага с добро управление на сесиите, възможност за опитимиране, имена на сесиите и многосесийни прозорци. Програмата също така ще ви спести време чрез автоматизиране на рутинни задачи по конфигуриране чрез мощни скриптове.

Промените можете да видите тук

Промените можете да видите тук

Все още няма добавени промени

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

Промените можете да видите тук

• With WYSE50 emulation, when the remote system sent ESC
• or ESC +, the reverse video attribute could remain set. SecureCRT now clears the display attributes when those escape sequences are received
  
• Escape sequences specifying that the entire display should be erased are now ignored when they contain an invalid parameter
  
• Added a global-file-only option "Log Uses Generic Write Flag" so that logging works with sessions that connect to a network drive that does not support the FILE_APPEND_DATA flag, such as Novell NSS
  
• Bug fixes

Все още няма добавени промени

• With WYSE50 emulation, when the remote system sent ESC
• or ESC +, the reverse video attribute could remain set. SecureCRT now clears the display attributes when those escape sequences are received
  
• Escape sequences specifying that the entire display should be erased are now ignored when they contain an invalid parameter
  
• Added a global-file-only option "Log Uses Generic Write Flag" so that logging works with sessions that connect to a network drive that does not support the FILE_APPEND_DATA flag, such as Novell NSS
  
• Bug fixes

• Mac: The permissions on the installer have been modified so that users other than the one who installed the application can run it.
  
• Mac: Improved the look of the button bar on the Retina display.
  
• SSH2: If an SFTP connection failed due to an "open channel" error, the SFTP tab incorrectly showed the connection status as connected.
  
• Windows: If a tabbed session was renamed so that it contained an ampersand, two ampersands were displayed in the tab, and the session name in the Activator did not contain any ampersands.
  
• Mac: If an application had been installed and then uncleanly uninstalled, SecureCRT crashed on startup.
  
• Mac/Linux: If the session option "Synchronize view to size" was set and the SecureCRT window was maximized and the font was small enough so that more than the maximum number of columns could fit in the terminal window, SecureCRT crashed.

• Mac: The permissions on the installer have been modified so that users other than the one who installed the application can run it.
  
• Mac: Improved the look of the button bar on the Retina display.
  
• SSH2: If an SFTP connection failed due to an "open channel" error, the SFTP tab incorrectly showed the connection status as connected.
  
• Windows: If a tabbed session was renamed so that it contained an ampersand, two ampersands were displayed in the tab, and the session name in the Activator did not contain any ampersands.
  
• Mac: If an application had been installed and then uncleanly uninstalled, SecureCRT crashed on startup.
  
• Mac/Linux: If the session option "Synchronize view to size" was set and the SecureCRT window was maximized and the font was small enough so that more than the maximum number of columns could fit in the terminal window, SecureCRT crashed.

Все още няма добавени промени

Все още няма добавени промени

• SecureCRT could crash if an SFTP tab was performing a transfer and the tabbed session that launched the SFTP tab was closed.
  
• If several tabbed sessions were connected and CTRL+TAB was used to cycle through them, the tab contents were not always updated.
  
• If a session could not be cloned because the channel connection failed, the cloned session's tab title was blank.
  
• SSH2: If a session specified a remote SFTP directory that contained an invalid character, such as "~", SecureCRT crashed when attemping to connect the SFTP tab.
  
• Windows: On Windows XP, if a session specified more than 140 local forwards, when the session connected, the forwards above the 140th failed.
  
• Mac: If a session had the "Scale the font" resize option set and SecureCRT was maximized, the last line was not visible.

• In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted.
  
• Opening the default session in a script caused SecureCRT to crash.
  
• If the "Automate logon" items for a session were re-ordered, the changes were not saved.
  
• If "/Serial" or "/Tapi" (Windows only) was specified on the command line, it was not honored.
  
• If a session that contained ANSI color text in the scrollback was disconnected and reconnected, the ANSI color attributes were no longer in the scrollback.
  
• When enough tabs were open to require the scroll control on the tab bar, if the right-most tab was activated and renamed, the tab bar shifted to the left and the active tab was no longer visible.
  
• Serial: The stop bits were not logged correctly in the trace output.
  
• SSH1/SSH2: If a session used a dynamic tunnel on port 10080 and another SSH1/SSH2 session went through the first session's SOCKS proxy and used a dynamic tunnel on port 1080, SecureCRT crashed when data went through the second tunnel.
  
• Windows: When switching between tiled and tabbed sessions in a maximized window, the terminal area was 24x80 instead of the full window area.
  
• Windows: If the global option "Minimize to Activator in system tray" was set and SecureCRT was closed, if "Connect" was selected from the Activator menu, the icons in the Connect dialog were not mapped to the correct actions.
  
• Mac: The session option "Use ALT as meta key" was not always honored.
  
• Mac: If the global option "Host key database location" was changed to a different path, the new path was not saved.
  
• Mac: If a session prompted for a log file, after the file location was selected, focus did not return to the SecureCRT window.

Changes:

• Mac: The look of text on Retina displays was improved.
  
• Linux: Character encodings that cannot be used by SecureCRT are no longer shown in Terminal/Appearance category in the Session Options dialog.

Bug fixes:

• If the protocol type was changed during authentication, SecureCRT crashed.
  
• If a session's emulation was set to "Dumb", it continued to used dumb emulation after being changed to use a different emulation.
  
• If a session reconnected automatically in the background when a different session's tab had focus, the title bar was updated to display the reconnected session name.
  
• Windows: If a laptop was docked such that a secondary monitor was used and then SecureCRT was moved to that monitor and closed, when the laptop was disconnected from the dock and SecureCRT was restarted, it was visible in the task bar, but not on the laptop display.
  
• Windows: On a system that had two monitors with the primary monitor having a larger display resolution than the secondary monitor, when SecureCRT was maximized on the primary monitor and then restored, it used the resolution of the secondary monitor.
  
• Windows: When the sessions were tiled, if the main window was resized, some of the tiled windows did not send a screen resize to the remote system.
  
• Mac/Linux: SecureCRT crashed after the Report button was pressed in the crash handler dialog.
  
• Mac/Linux: If data was being output and the scrollbar was used to look at data in the scrollback buffer, the output was not paused.
  
• Mac: Passwords specified on the command line were ignored if the global option "Use Keychain" was set.
  
• Mac: If the global option "Show confirm disconnect dialog" was set and multiple SecureCRT windows with connected sessions were open and then one window was closed, attempting to switch between the remaining windows using COMMAND+` did not work.
  
• Mac: When SecureCRT was not set as the default Telnet handler and the default Telnet handler check was on, a message was displayed every time SecureCRT went into or out of "Full Screen" mode.
  
• Linux: Error text was not displayed correctly on Ubuntu with the Korean language pack installed and set as the primary language.

Changes:

• The xterm set title escape sequence ending with \033\\ is supported in addition to \007.

Bug fixes:

• If the username was sent to a session after the connection was gone, such as when the server had a short authentication timeout, SecureCRT crashed.
  
• Hostkey database paths that contained "%USERPROFILE%" were not expanded correctly.
  
• If a disconnected session had focus and other tabbed or tiled sessions were connected and the "Show confirm disconnect dialog" option was set, SecureCRT did not display the disconnect prompt when the application was closed.
  
• Windows: SHIFT+INSERT could not be used to paste into the Connect bar.
  
• When SecureCRT and SecureFX were integrated, if the configuration folder contained "%APPDATA%", attempting to launch SecureFX from the SecureCRT toolbar caused an error to be reported.
  
• The ConnectInTab script function did not honor the "Reuse disconnected tabs" setting.
  
• Windows: After maximizing and restoring a tiled session, the output was displayed in only the top half of the session window.
  
• Windows: When a SecureCRT session was launched from the Windows 7 task bar "Connect..." menu item, it was displayed behind all other application windows.
  
• Windows: A custom menu file configured in SecureCRT 6.7 did not take effect after installing version 7.0 until SecureCRT was closed and restarted.
  
• Windows: When SecureCRT started in tabbed mode after switching between tabbed and tiled windows that connected sessions with small sizes, the application window was smaller than the specified session size.
  
• Windows: When the Windows 7 task bar was not in the default location, and SecureCRT switched from tiled to tabbed mode, the tab bar was not in the correct location.
  
• Windows: The New Session wizard allowed a session to be created with a name that was a Windows reserved keyword, such as COM1 or LPT1.
  
• Mac: SecureCRT could not be installed on OS X 10.8 (Mountain Lion) without disabling the gatekeeper.
  
• Mac: After creating a new or editing an existing color scheme, the Global Options dialog became unresponsive.
  
• Mac: SecureCRT could hang when configuring the tab status indicator rectangle colors.
  
• Mac: Pressing CTRL+TAB or CTRL+SHIFT+TAB did not switch to the next or previous tabs, respectively.
  
• Mac: When SecureCRT was minimized to the dock, it could not be restored by left-clicking it.
  
• Mac: On OS X 10.8 (Mountain Lion), SecureCRT could not locate crash dump files because they were being created in a different folder than in previous versions of OS X.
  
• Mac: The title bar was displayed in full-screen mode.
  
• Linux: SecureCRT prompted when the log file existed, although the "Append to file" option was set.

• SSH1/SSH2: When a window decoration such as the chat window or
  button bar was toggled, or the Session or Global Options dialog
  was closed, IPv6 listening ports being used for tunneling were
  closed.
  
• Windows: When the mouse hovered over the button bar field in the
  button bar, SecureCRT could crash.
  
• Mac/Linux: If the tab status indicators were set to "Colored
  rectangles", SecureCRT crashed when trying to lock a tabbed
  session.

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Все още няма добавени промени

Коригирани грешки:

• 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.
  
• Windows: 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.
  
• Mac/Linux: When a button was added to the button bar while a session was connected, the session size decreased.
  
• Linux: On Ubuntu Linux, the evaluation was not extended after the evaluation extension data was entered.

Коригирани грешки:

• 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.
  
• Windows: 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.
  
• Mac/Linux: When a button was added to the button bar while a session was connected, the session size decreased.
  
• Linux: On Ubuntu Linux, the evaluation was not extended after the evaluation extension data was entered.

Нововъведения:

• Added support for Ubuntu Linux 11.10. 32-bit and 64-bit installers are available.
  
• Added support for Red Hat Enterprise Linux 6.0. 32-bit and 64-bit installers are available.

Коригирани грешки:

• 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%.
  
• Mac/Linux: If the Public Key Assistant was used to generate a DSA key in OpenSSH key format and then upload the key file, the file had 0644 permissions instead of 0600 permissions, which meant that OpenSSH refused to use it.
  
• Mac/Linux: If a license field, such as Name or Company Name, contained more than one line of text, the license was accepted, but could not be used when SecureCRT restarted.
  
• Mac: On a system that previously had SecureCRT installed, after upgrading to OS X Lion, SecureCRT could not save license information.
  
• Mac: On OS X Lion, the prompt for making SecureCRT the default Telnet application continued to be displayed when SecureCRT restarted after answering "Yes" to the prompt.
  
• Mac: With the "Autoreconnect" option on, when a session connected through a forwarded port established by another session and a local session was also connected, if the sessions became disconnected, they did not reconnect automatically.
  
• Linux: After exiting a local shell session, an I/O error was reported.
  
• Linux: It was not possible to store passwords using the Password Properties dialog.

Нововъведения:

• Linux: Added support for Ubuntu 11.04.

Промени:

• Windows: The 32-bit installer can be installed on a 64-bit system.
  
• Linux: Added an accelerator (ALT+M) to toggle the menu bar.

Коригирани грешки:

• 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.
  
• Mac: If the system language was set to Russian, SecureCRT crashed when it was launched.
  
• Mac: Mapping a button on the button bar to launch an application did not work.
  
• Mac: After going into full screen mode and connecting to another session, the last line of the new session was cut off.
  
• Mac: The "Public Key Wizard" dialog was taller than necessary.
  
• Mac/Linux: It was not possible to double-click a port forward item in order to open its "Properties" dialog.
  
• Linux: Opening URLs did not work.
  
• Linux: On Ubuntu, attempting to register SecureCRT by pressing the "Enter License Data" button on the dialog that appeared after the evaluation license expired did not work.

Все още няма добавени промени