Hi Mike..
Thanks for the note on the telnet stuff etc.. versus using ssh clients.
Won't work for what I need to do. What I am after is to have one of my
telnet ports used for people to telnet to an amateur radio node. You need to
use normal telnet for that and by default people assume port 23 is used to
telnet to the service , so everything works fine. Now, port 24 is left for
people to telnet to your Kernel and that one could be ssh for sure. At least
I think so..
So, it is a Radio Amateur Service that I am playing with so things are a
little different. And as far as I know ssh will not work through a node
where one is communicating with rf connections and other nodes..
On Sunday 29 April 2001 11:24 pm, you wrote:
> On Sun, 29 Apr 2001, Ted Gervais wrote:
> >> Telnet is run under xinetd.d not services, so what I guess I would had
> >> done is in /etc/xinetd.d/ dir made a copy of telnet to telnet2 and just
> >> edit telnet2 for your port to use. Then disable telnet and enable
> >> telnet2, then restart xinetd.
> >
> >Hi Mike..
> >
> >Well - I need both port 23 and 24 for telnetting. By default I need port
> > 23 for the unknowns who telnet and don't know I have another service. So,
> > port 23 serves that service. And then there is port 24 for other telnet
> > services..
>
> That won't fool anyone. A portscanner will show up something
> listening on port 24 very easily. It doesn't take much after
> that to determine it is telnet.
>
> If you are wanting to connect to your machine in a secure way,
> totally remove telnet from the system completely, and install
> openssh (which comes with Seawolf).
>
> ssh is much more secure. ssh clients abound for any OS.
--
Ted Gervais
Coldbrook, Nova Scotia Canada.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
