１）/etc/rc.d/init.d/sshd start でSSHサービスを起動する
２）/etc/xinetd.d/telnet ファイルを編集し、disable = yes にする。
３）/etc/rc.d/init.d/xinetd restart でサービスを再起動する。
TTSSH: An SSH Extension to Teraterm
By Robert O'Callahan (firstname.lastname@example.org)
Various traffic analysis vulnerabilities have been discovered in the SSH protocol. TTSSH has been modified to provide as much protection as anyone knows how to provide. The modified version is TTSSH 1.5.4.
Many people ask me whether or not TTSSH will support SSH protocol version 2. It does not and it will not. There is an SSH2-capable Teraterm available from Yutaka Hirata. Note that I have not used it and cannot vouch for the code. Putty is also a good free SSH2-capable Windows SSH client.
What TTSSH Is
TTSSH is a free SSH client for Windows. It is implemented as an extension DLL for Teraterm Pro. Teraterm Pro is a superb free terminal emulator/telnet client for Windows, and its source is available. TTSSH adds SSH capabilities to Teraterm Pro without sacrificing any of Teraterm's existing functionality. TTSSH is also free to download and use and its source is available too, with an open source/free software license. Furthermore, TTSSH has been developed entirely in Australia, and can be exported from here to anywhere in the world (apart from places where people aren't allowed to own cryptographic software at all :-( ). There is even some documentation.
To be more precise, the current version of TTSSH (1.5.4) includes the following features:
- Compatible with SSH protocol version 1.5
- Ciphers: 3DES, Blowfish, DES (RC4 and IDEA are also included but must not be used)
- Server authentication using the ssh_known_hosts database (including the option of adding a server's key to the database)
- Authentication using password, RSA, rhosts, rhosts+RSA, TIS challenge/response
- Compression support
- Connection forwarding, including full support for X connection forwarding
Note that TTSSH is just an SSH client and does not include any other SSH tools (scp, ssh-keygen, ssh-agent, etc). Furthermore, because it's tied into Teraterm, it's only suitable for interactive use. For non-interactive uses such as interprocess communication, you want a straight port of the Unix client.