Telnet - Encryption

Hello, 2 things: 1) Telnet encryption for Linux needs to be implemented to replace telnetd service with compiled telnetd that uses RC4 authentication method. I need the complete step-by-step procedure on recompiling the telnetd to use RC4 encryption method. 2) Able to telnet into encrypted telnetd server, with the step by step procedures that will allow my telnet client (using puttySSH) to send the encrypted chars to "encrypted" compiled telnetd server. This should be a simple project. Looking forward to work with the right Linux guru with encryption knowledge. ============================ Additional description: 1) First, please look into [login to view URL]~dholland/computers/[login to view URL] to understand the netkit history. 2) Look into Redhat/Fedora SRPMS for telnet, which contains netkit-telnet-0.17 tarball. If you do not have it, get it and download it from various sources, then untar it to your linux, and then go to telnetd (and telnet) directory, which you will see source code files there. 3) The objective for this one is to compile the telnetd (written in C) using RC4 (my own function, written in C) that will de-encrypt and encrypt every line based on RC4. See login example below Example: Server/Client Chars Description/Notes ServerSend> login: (encrypted to #$^#$^) ClientRead> #$^#$^ (de-encrypted to login:) ClientSend> RobName (encrypted to DS#D^^*) ServerRead> DS#D^^* (de-encrypted to RobName) ServerSend> password: (encrypted to DE%$^%S^A/) ClientRead> DE%$^%S^A/ (de-encrypted to password:) ClientSend> 334pass% (encrypted to #$;4#^0i ) ServerRead> #$;4#^0i (de-encrypted to 334pass% ) ... ... It should be a simple implemention task. The modified telnet (to be used for test) will need to prompt the key code to be entered when telnetting into modified telnetd server. Reason: I have my embedded board that has TCP/IP stack. It will not handle SSH engine due to heavy process overhead. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Linux 2.4 with telnetd (see netkit for details) C programming