깔끔하고 안정적인 텔넷 SecureCRT v6.5.3 32/64비트

 

Van Dyke Technologies, Inc.(http://www.vandyke.com)에서 제작한 SecureCRT는 강력한 기능성에 보안기능까지 첨가된 텔넷 프로그램입니다. 5월 11일 릴리즈 되었으며 30일동안 이용 가능합니다.

 

SecureCRT는 기존의 유명 텔넷 클라이언트 프로그램인 CRT의 발전된 형태로 다양하고 고급 기능을 포함시켜 쉬운 인터페이스와 2바이트 문자의 지원으로 한글 사용이 원활하다는 점과 편리한 다운로드와 업로드 기능을 가지고 있어 많은 사랑을 받고 있습니다. 또한 자동 로그인 기능과 사용자가 만들 수 있는 키맵 등 다양한 기능을 지원하고 있습니다. SecureCRT는 CRT에서 제공되던 기본 기능에, SSH1, SSh2, Telnet, rlogin, serial, TAPI 등의 프로토콜을 지원합니다.

SSH2는 패스우드를 통한 암호 증명과 Public Key 인증과 함께 AES, 3DES, RC4, Blowfish, Twofish 암호를 제공합니다.
이외에, VT100, VT102, VT220, Linux 등과 ANSI 터미널 에물레이션 연결이 가능하고 한글문자에 대한 지원과 ANSI 컬러가 지원이 됩니다.
 

주요기능

 

- 원거리 사이트 접근
- ANSI 컬러를 지원
- 다양한 터미널 모드 지원(VT100, VT102, VT220 과 ANCI 터미널)
- Zmodem, Xmodem 파일 전송
- Visual Basic Script 지원
- Microsoft Java script 지원
- 키보드 특정키를 원하는 것으로 정의

 

개선사항

 

- After changing the selected button bar in the drop-down list, focus is returned to the active session.

- 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.

 

SecureCRT v6.5.3 32비트 다운로드

SecureCRT v6.5.3 64비트 다운로드