SecureCRT for Windows, Mac, and Linux provides rock-solid terminal emulation for computing professionals, raising productivity with advanced session management and a host of ways to save time and streamline repetitive tasks. SecureCRT provides secure remote access, file transfer, and data tunneling for everyone in your organization.
Whether you are replacing Telnet or Terminal, or need a more capable secure remote access tool, SecureCRT is an application you can live in all day long. With the solid security of SSH, extensive session management, and advanced scripting, SecureCRT will help raise your productivity to the nth degree.
- Securely access business applications on UNIX, Linux, or VMS from machines running Windows, Linux, and Mac - employ the rich emulation support for VT100/102/220, TN3270, ANSI, SCO ANSI, Wyse 50/60, Xterm, and Linux console
- Configure, manage, and organize all your sessions with full control over scrollback, key mappings, colors, fonts, and more - whether you have one or thousands of sessions.
- Access your full array of network devices from one client with SSH2, SSH1, Telnet, Telnet/SSL, serial, and other protocols.
- Leverage the high-productivity UI with time-saving capabilities including multi-session launch, tabbed sessions, tiled sessions, cloned sessions, a button bar for repeated commands, and mapped keys.
- Depend on the open standard Secure Shell protocol for encrypted logon and session data, flexible authentication options, and optional FIPS 140-2 -approved ciphers.
- Automate repetitive tasks in SecureCRT by running scripts using VBScript, JScript, PerlScript, or Python. The script recorder builds your keystrokes into a VBScript or Python script.
- Transfer files between network devices with SFTP, Xmodem, Ymodem, Zmodem, or Kermit. A built-in TFTP server provides additional file transfer flexibility.
- Save steps with the close integration of SecureCRT and the SecureFX file transfer client, which share sessions and settings that let you run SFTP, FTP, SCP, and FTP/SSL file transfer sessions without reentering passwords.
This software is subject to export control and may be transmitted, exported, or re-exported only under applicable export laws and restrictions and regulations of the United States Bureau of Export Administration or foreign agencies or authorities. By downloading or using the software, you are agreeing to comply with export controls.
SecureCRT is now available for export to most individuals and organizations worldwide under the Export Administration Regulations (EAR) of the U.S. Bureau of Export Administration (BXA) governing strong encryption software. No restrictions apply to customers located in member states of the European Union (EU) and nine other countries. Restrictions apply to certain government users in other countries.
You will be asked to fill out an eligibility declaration before downloading.
What's new in version 8.3.3?
- Added a global option to disable all printing.
- ssh-add can be used to add keys from a remote Linux, Unix, or Mac
- system to SecureCRT's agent using agent forwarding.
- Mac: The accelerator for resetting the zoom level to 100% was changed to COMMAND+SHIFT+0.
- SecureCRT crashed when the remote system tried to write to the VT320 status line, but the VT320 status line had not been enabled by the remote.
- SecureCRT did not send FIN when disconnecting Telnet sessions.
- If the SecureCRT window was maximized and then minimized and restored, when a session was connected, the window was restored instead of remaining maximized.
- The hostname was not remembered if the protocol was changed from SSH2 to Telnet when the Connect bar was used to connect to a remote system.
- In Python scripts, the Session object method "Unlock" did not work.
- Windows: On Windows 10, if RDP was used to connect to a machine running SecureCRT with a session connected and then RDP was disconnected, SecureCRT crashed.
- Mac: If focus was in the Connect bar and text was entered causing the auto complete dropdown to be displayed, SecureCRT crashed if it
was closed using the red "X".
- Mac: If the user didn't have write permission to the /cores file, a warning was displayed when SecureCRT started.
- Mac: Keymapping did not work correctly when a key was mapped to COMMAND+X.
- Mac: In the Color Scheme dialog, the scrollbar thumb became unresponsive when it was dragged to scroll the ANSI colors list.
- Mac: In a Python script that created a message box with "Yes" and "No" buttons, the default button could not be set to "No".
- Linux: On Ubuntu, after selecting a session in the Session Manager or Connect dialog, it could take a long time to connect the session
or display the session's properties.
Note: In order to use SecureCRT's SSH protocol support, you must have access to a SSH server, like: VShell. If you are not sure, check with your ISP or local network administrator.
Secure CRT and Secure FX are available as a bundle.
For SecureCRT and SecureFX bundle pricing click here
SecureCRT and SecureFX bundle