Create a branch for header work.
[reactos.git] / base / applications / network / telnet / doc / ssh.txt
1 It should be possible to add ssh support to console telnet, as console telnet has a very modular design when it comes to the networking code. There is already support for pipes, and if there exists an ssh client for Win32 that will output to stdout, then you're in business. I'm yet to find such a client, but if one existed, an SSH session could be started like so:
3 C:\> telnet
4 Copyright message, license.txt, stuff, etc.
5 telnet> set io_netpipe "C:\BIN\SSH.EXE -l username host"
6 telnet> open blah
7 login:
8 password:
10 Unfortunately, all the ssh clients I've found don't work this way. You can output CMD.EXE to telnet this way, though, and get a very pretty ansi interpreter. If you want to try to get OpenSSH working, here's step-by-step instructions to get you started (please read them all the way though):
12 1) Get Perl from
13 2) Get Openssl from
14 - Follow directions in INSTALL.W32
15 - Copy the .LIB files from OUT32DLL to your LIB directory (C:\DevStudio\VC\LIB)
16 - Copy the .DLL files from OUT32DLLto your system directory (C:\Winnt\System32 or C:\Windows\System)
17 - Copy the .H files from INC32\OPENSSL to your include\ssl (C:\DevStudio\VC\include\ssl)
18 - Copy these same files to include\openssl (C:\DevStudio\VC\include\openssl)
19 3) Get Openssh from
20 4) Modify Openssh so it will compile, and get rid of all the termios stuff
22 Obviously this is a lot of work. If you need a good ssh client, try PuTTY from It may be possible to integrate PuTTY and Telnet, and that would certainly be easier than the above option. PuTTY is licensed under the MIT license, which seems to be compatible with the GPL. The primary advantage of integrating the two projects is that PuTTY would gain the key mappings that telnet has, and telnet would gain encryption.