From owner-freebsd-questions  Sun Sep 21 19:25:38 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA03367
          for questions-outgoing; Sun, 21 Sep 1997 19:25:38 -0700 (PDT)
Received: from pili.adn.edu.ph (pili.adn.edu.ph [165.220.57.4])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA03362
          for <questions@FreeBSD.ORG>; Sun, 21 Sep 1997 19:25:32 -0700 (PDT)
Received: from localhost (art@localhost)
	by pili.adn.edu.ph (8.8.5/8.8.5) with SMTP id TAA01310;
	Sat, 20 Sep 1997 19:08:13 +0800 (PHT)
Date: Sat, 20 Sep 1997 19:08:13 +0800 (PHT)
From: Arthur Alacar <art@pili.adn.edu.ph>
To: Doug White <dwhite@resnet.uoregon.edu>
cc: questions@FreeBSD.ORG
Subject: Re: telnet restriction.
In-Reply-To: <Pine.BSF.3.96.970919233100.716T-100000@gdi.uoregon.edu>
Message-ID: <Pine.BSF.3.95q.970920190303.1247A-100000@pili.adn.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> So you want to keep people from telnetting to ports other than the
> standard telnet port, 23?
> 
> You might be able to do it with tcp_wrappers, write a script that strips
> off the final argument, or modify the telnet source to hardware the
> destination port.

modify telnet source?.. well.. it could simply be done....as a matter of
fact.. i have changed the permission for this telnet command... but
unfortunately we have this some 'brilliant' users... who happened to get a
copy of this telnet file (saving it on his home dir) and used it..... so
this mechanism failed.

|art|