From: treason@gnu.ai.mit.edu
To: cypherpunks@toad.com
Message Hash: a7cbe39b8a7faa26fb30eae6f2114fa0254e6f8a277f97c0daaca9a786945545
Message ID: <9308092013.AA07670@spiff.gnu.ai.mit.edu>
Reply To: N/A
UTC Datetime: 1993-08-09 20:16:37 UTC
Raw Date: Mon, 9 Aug 93 13:16:37 PDT
From: treason@gnu.ai.mit.edu
Date: Mon, 9 Aug 93 13:16:37 PDT
To: cypherpunks@toad.com
Subject: Using a 'telserv' program to redirect mail
Message-ID: <9308092013.AA07670@spiff.gnu.ai.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain
I know the subject is misleading but to get into the heart of the matter.
It is very simple to write a unix program to redirect a program driving
a port to another port without affecting it running on the first port. The
program I have seen to do this is called 'telserv' and can redirect any
port daemon to operate on any other port available (above 1024 of course)
without any special system access. With this program I have been able to
redirect telnetd, ftpd, and smtpd to other ports with no problem. In most
cases, the new port is not logged, and works 100% accurately. The only
current limitation is that only one port process can be taking place at a time.
This could easily be surpassed by a simple fork() statement addin. I will
not post this code unless I am assured that it is not going to be a legal
problem. As you can see from the above written statement, I am not a learned
unix programmer, as I have taught myself everything I know (the only accessible
machine our uni has is a prime 6250), so please be gentle with the flames, I
have done my best to represent the code and system accurately.
treason@gnu
Return to August 1993
Return to “treason@gnu.ai.mit.edu”
1993-08-09 (Mon, 9 Aug 93 13:16:37 PDT) - Using a ‘telserv’ program to redirect mail - treason@gnu.ai.mit.edu