Subject: Re: moving telnet to another port
To: Dr. Bill Studenmund <wrstuden@loki.stanford.edu>
From: David Brownlee <abs@anim.dreamworks.com>
List: port-mac68k
Date: 11/05/1998 16:55:32
	They would if they portscanned :)

	A better option might be to look at ssh (from pkgsrc), but that
	depends on you having an ssh client at the other end.

		David/absolute

	Abandoning a syncing disk... or syncing an abandoned disk?

On Thu, 5 Nov 1998, Dr. Bill Studenmund wrote:

> On Thu, 5 Nov 1998, Joshua E Hope wrote:
> 
> > I don't know about security issues, but I do know you'd have to edit
> > /etc/services not inetd.conf :)
> 
> I think editing /etc/services to renumber the telnet service would be a
> mistake. Either just camp telnet on another service's port, or add
> something like a "joetelnet" at a new port #.
> 
> I'm not sure what all uses /etc/services (other than inetd, obviously :-)
> , but have the gut instinct that changing "well-defined" values to
> non-standard ones can cause a problem. Or more accuratly, it might  cause
> one a while in the future.
> 
> > On Thu, 5 Nov 1998, Joe Laffey wrote:
> > 
> > > If I'd like to move telnet from port 23 to another port (say 2300) are
> > > there any security issues I need to watch out for? Is it simply a matter
> > > of adding another entry in my inted.conf file and commenting out the
> > > telnet entry?
> 
> Nope, that's it. Your telnet will still be as (in)secure as before, just
> external intruders won't know where to look for it.
> 
> Take care,
> 
> Bill
>