At 4/11/01 11:54 AM -0300, you wrote:
>Thanks for the response. I just did a grep to see if xinetd is running.
Have you actually checked that the service is not disabled?
Type:
chkconfig --list telnet
and see if it's on. It it's off, you can enable it with:
chkconfig telnet on
Then restart x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 11 April 2001 16:08, you wrote:
> Openssh uses the openssl libraries, which are licensed for export. I think
> that as long as you don't plan on communicating with someone in North
> Korea or Libya, you will be fine.
>
> thornton
yes, bu
On Wed, 11 Apr 2001, Bryan Fields wrote:
> I don't know what the Canadian Gov says about encryption over amateur radio
> packet, but I know that in the FCC says it is illegal to do it. Of course i
> am assuming this is going to be used over amateur radio.
Openssh uses the openssl libraries, wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 11 April 2001 11:03, you wrote:
> On Wed, 11 Apr 2001, Ted Gervais wrote:
> > Yup on the SSH. But I am not sure that SSH will work over Packet Radio.
> > Whereas Telnet does. But it is a good thought..
>
> If it uses TCP, then it will wor
On Wed, 11 Apr 2001, Thornton Prime wrote:
That sounds so simple. You have done this before Thornton. Thanks for the
tip. I will try that right away..
>
> With xinetd, you should be able to copy /etc/xinet.d/telnet to
> /etc/xinet.d/telnet2 and then copy add a line in /etc/services that says
>
On Wed, 11 Apr 2001, Mike Chambers wrote:
The two telnet ports are need so that the average user that logs in, gets
the packet radio node. Not the kernel. But if someone wants to telnet into
your linux system (kernel) then there is port 24. So the default becomes
23 rather then 24 and life is gre
On Wed, 11 Apr 2001, you wrote:
> > Heh... of course, you ARE aware that SSH is better than telnet in 99% of
> > the cases where you're going to use telnet... ;-)
>
> Yup on the SSH. But I am not sure that SSH will work over Packet Radio.
> Whereas Telnet does. But it is a good thought..
>
Ahh.
With xinetd, you should be able to copy /etc/xinet.d/telnet to
/etc/xinet.d/telnet2 and then copy add a line in /etc/services that says
telnet2 24/tcp
One instance of xinetd should be fine to serve telnet on both ports 23 and
24.
thornton
On Wed, 11 Apr 2001, Mike Chambers wrote:
>
> ORIGINAL MESSAGE BELOW
>Hi Mike..
>
>Sounds great. And it even sounds easy. Not tell me, is it possible to have
>telnet available on ports 23 and 24? That would mean two of those files. I
>guess you could call them xinetd-1 and -2 ?? Would that be the way to do it?
That's
On Wednesday 11 April 2001 13:03, you wrote:
> On Wed, 11 Apr 2001, Ted Gervais wrote:
> > Yup on the SSH. But I am not sure that SSH will work over Packet Radio.
> > Whereas Telnet does. But it is a good thought..
>
> If it uses TCP, then it will work with ssh.
>
> There is a little bit more over
On Wednesday 31 December 1969 20:00, you wrote:
> You won't find what your looking for in /etc/xinetd.conf. To
> modify/edit any of the services you found in inetd you need to go to
> /etc/xinetd.d/ directory. The services in that directory are each an
> executable file that you edit seperately
Hi Thorton.
Thanks again for the quick response. I have it working now. I saw that it was
off when I ran chkconfig so knowing this I turned it on. Works fine now.
And I agree with SSH versus telnet but I use the telnet service for Packet
Radio, which transmits radio data across airways and the
On Wed, 11 Apr 2001, Ted Gervais wrote:
> Yup on the SSH. But I am not sure that SSH will work over Packet Radio.
> Whereas Telnet does. But it is a good thought..
If it uses TCP, then it will work with ssh.
There is a little bit more overhead, so you might see more latency, but
you might be a
On Wednesday 11 April 2001 11:48, you wrote:
> On Wed, 11 Apr 2001, you wrote:
> > Hi John..
> > I am familiar with inetd.conf as well. That is what is making things so
> > confusing. I will have a look at xinetd.conf but that has very little in
> > it. And of course I have looked at all the files
m: Ted Gervais <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Re: Telnetting
>Reply-To: [EMAIL PROTECTED]
>
>
>Hi John..
>I am familiar with inetd.conf as well. That is what is making things so
>confusing. I will have a look at xinetd.conf but that has very
On Wed, 11 Apr 2001, Ted Gervais wrote:
> Thanks for the response. I just did a grep to see if xinetd is running.
> Here is what I see:
>
> [root@mach3 init.d]# ps ax | grep xinetd
> 814 ? S 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
>
> Does that look right?
Looks go
On Wed, 11 Apr 2001, you wrote:
> I just tried that and it says telnet off. How come? So as you said I ran
> chkconfig telnet on, and away it went.!!
>
>
> Thank you very much for helping me out here. Isn't a fix easy when one
> knows the answer.
>
>
> One last question - how come that serv
On Wed, 11 Apr 2001, you wrote:
>
> Thanks for the response. I just did a grep to see if xinetd is running.
> Here is what I see:
>
> [root@mach3 init.d]# ps ax | grep xinetd
> 814 ? S 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
>
> Does that look right?
>
> Afterthat
On Tue, 10 Apr 2001, Thornton Prime wrote:
>
> On Tue, 10 Apr 2001, Ted Gervais wrote:
> >
> > So - what am I missing that will allow telnetting to my system. Here is the
> > error people see:
> >
> > [ve1drg@mach3 ve1drg]$ telnet 142.176.139.108
> > Tr
On Tue, 10 Apr 2001, Chad W. Skinner wrote:
> Check your xinet.d directory for the telnet configuration file and make sure
> it is not disabled. Also, if you enable it or have not already done so, be
> sure you restart xinetd.
Hi Chad.
Thanks for the response. I just did a grep to see if xinet
On Wed, 11 Apr 2001, you wrote:
> Hi John..
> I am familiar with inetd.conf as well. That is what is making things so
> confusing. I will have a look at xinetd.conf but that has very little in
> it. And of course I have looked at all the files in /etc/rc.d/init.d
> directory.. If I could just cha
gt; Well I did that. I went and found the rpm files and installed them. Before I
> > did that no one could telnet to me. After I did this, still no one can telnet
> > to me.
> >
> > So - what am I missing that will allow telnetting to my system. Here is the
> >
On Tue, 10 Apr 2001, Ted Gervais wrote:
>
> So - what am I missing that will allow telnetting to my system. Here is the
> error people see:
>
> [ve1drg@mach3 ve1drg]$ telnet 142.176.139.108
> Trying 142.176.139.108...
> telnet: Unable to connect to remote host: Connection re
Check your xinet.d directory for the telnet configuration file and make sure
it is not disabled. Also, if you enable it or have not already done so, be
sure you restart xinetd.
Chad
> Thanks to all who responded to my query about installing telnetd
> and that I
> should really install the telnet
to me. After I did this, still no one can telnet
> to me.
>
> So - what am I missing that will allow telnetting to my system. Here is the
> error people see:
>
> [ve1drg@mach3 ve1drg]$ telnet 142.176.139.108
> Trying 142.176.139.108...
> telnet: Unable to connect to remot
- what am I missing that will allow telnetting to my system. Here is the
error people see:
[ve1drg@mach3 ve1drg]$ telnet 142.176.139.108
Trying 142.176.139.108...
telnet: Unable to connect to remote host: Connection refused
What am I missing..
--
Ted Gervais
Coldbrook, Nova Scotia Canada
Another possible solution is the perl Telnet package, which will allow you
to automate login/password and execute a command.
But that requires a little Perl knowledge. :)
D
At 11:24 AM 6/22/98 -0400, you wrote:
>Try "expect".
>
> _
Try "expect".
__
| Bryan Swann ([EMAIL PROTECTED]) 803/566-0086 803/554-0015 (Fax) |
| Eagan McAllister Associates, Inc.|
|
On Sat, 20 Jun 1998 23:49:07 -0700 (PDT), GateKeepeR News wrote:
>Hi,
>Looking for a way to setup a script so I can telnet into a certain port
>on my box, it would prompt for a username, I would type a user and press
>enter, then it would prompt for a message, i would type it and press
>enter. Th
Why don't you just use a shell script as a login shell for a new account
that you'd use only for such purposes? If you want to listen on a
particular port, you'll prolly need something more than a bash script.
Here's something simple that you might set as a login shell on a new
account(warnin
Hi,
Looking for a way to setup a script so I can telnet into a certain port
on my box, it would prompt for a username, I would type a user and press
enter, then it would prompt for a message, i would type it and press
enter. Then it would take that and maybe use the write command to write
it to th
31 matches
Mail list logo
