<snip>the d is for daemon, a process which runs inside the machine and
provides a service</snip>
t is for telnet
it's insecure and bad
s is for secure
the shell that must be had
d is for daemon
the way that things are run
f is for firewall
that blocks connect-ions
I'm sorry, it's Friday after all and your comment about d made me think
of the old Cookie Monster Favorite, C is for cookie. I hope the list can
forgive me.
Rodolfo J. Paiz wrote:
> At 4/19/2002 09:59 AM -0500, you wrote:
>
>> I am new to the Linux World and trying to understand the language
>> spoken here.
>
>
> You're going to read *lots* of documentation and man pages, but you'll
> be fine. The effort is certainly worth it.
>
>> I have just installed RH 7.1 running Apache and I am having problems
>> using telnet and puTTY.
>> Does a telnet daemon need to be running to used ssh?
>> If I try to telnet to my IP address I get "can not open connection to
>> ...address....
>> If I use putty ip address a window flashes and goes await
>> or I get "connection closed by remote host".
>
>
> Telnet is a program to supply a remote terminal to someone; so is ssh.
> However, telnet sends everything (including your username and password)
> in the clear, where anyone sniffing the network can see *everything* you
> type whereas ssh (which stands for Secure SHell) encrypts the entire
> transaction so that everything you type is nearly impossible to
> intercept or decrypt.
>
> Hence, use telnet only when you really truly have to and when you're in
> an internal trusted network. But given that ssh has some other neat
> features, everyone will strongly recommend to you that you try to use
> ssh everywhere. They are independent; telnet does not need to run (or
> even be installed) for ssh to work and vice versa.
>
> That being said, the most common package for SSH capability (included
> with RedHat) is openssh. Your Linux box must have the openssh and
> openssh-server packages installed, plus (optionally) the openssh-client
> package. Once the packages are installed, as root issue the commands:
>
> # service sshd start
> # chkconfig --level 2345 sshd on
>
> The first will start sshd (the d is for daemon, a process which runs
> inside the machine and provides a service), and the second will make
> sure that sshd is started when you change runlevels or reboot.
>
> You also want to make sure that you do not have a firewall blocking that
> traffic. Do you have a firewall configured at all?
>
> Let us know whether you get this working, or provide more detail and ask
> very specific questions.
>
>
--
Matthew Boeckman (816) 777-2160
Manager - Systems Integration Saepio Technologies
==
==
/earth is 98% full ... please delete anyone you can.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
