for telnet
> system-config-nfs — Fedora's graphical Network File System configuration tool
> system-config-network — Fedora's graphical network and service management client for X
> system-config-securitylevel — Fedora's graphical firewall configuration utility
Reference
The following websites and books are great resources for more information on the topics covered in this chapter. Networking is complex. The more you take the time to learn, the easier setting up and maintaining your network will be.
General
> http://www.ietf.org/rfc.html — Go here to search for, or get a list of, Request For Comments (RFC).
DHCP
> http://www.oth.net/dyndns.html — For a list of Dynamic DNS service providers, go to this site.
> http://www.isc.org/products/DHCP/dhcpv3-Read Me.html — The DHCP Read Me is available at this site.
Wireless
> http://www.ieee.org — The
> http://www.mozillaquest.com/Network_02/Wireless_Network_Technology_03_Story- 01.html — Wireless networking with Red Hat 7.2.
> https://agora.cs.uiuc.edu/display/tsg/Technology+Services+Group+Home — Wireless networking using Red Hat Linux at the
> http://www.sorgonet.com/network/wirelessnoap/ — Building a wireless network without using an access point, using Red Hat 8.0.
Books
>
>
>
>
CHAPTER 15
Remote Access with SSH
The ability to control your system remotely is one of the high points of Fedora Core Linux — you can connect from any Linux box to another Linux box in a variety of ways. If you just want to check something quickly or if you have limited bandwidth, you have the option of using only the command line, but you can also connect directly to the X server and get full graphical control.
Understanding the selection of tools available is largely a history lesson. For example, Telnet was an earlier way of connecting to another computer through the command line, but it has since been superseded by SSH. That is not to say that you should ignore Telnet; you need to know how to use it so that you have it as a fallback. However, SSH is preferred because it is more secure. We cover both in this chapter.
Please keep in mind that although Telnet is worth keeping around as a fail-safe, last-resort option, SSH is superior in virtually every way. Telnet is fast but also insecure. It sends all your text, including your password, in plain text that can be read by anyone with the right tools. SSH, on the other hand, encrypts all your communication and so is more resource intensive but secure—even a government security agency sniffing your packets for some reason would still have a hard time cracking the encryption.
Andy Green, posting to the fedora-list mailing list, summed up the Telnet situation perfectly when he said, 'As Telnet is universally acknowledged to encourage evil, the service telnetd is not enabled by default.' It is worthwhile taking the hint: Use Telnet as a last resort only.
Setting Up a Telnet Server
Having been superseded by SSH, you will find the Telnet server installation packages under Legacy Network Server in the Add or Remove Packages dialog box. You need to select it from the Details selection because it is not one of the default selections for the package group. After it's installed, select System Settings, Server Settings, Services and enable Telnet for runlevel 5. Note your IP address while you are here (switch to root and run ifconfig).
With that done, you can now fire up your other Linux box and type telnet <. If you are unsure of your IP address, switch to root and use the ifconfig command. You are prompted to enter your username and password. The whole conversation should look like this:
[paul@susannah ~]$ telnet 10.0.0.1
Trying 10.0.0.1...
