Red Hat Certified Engineer Tutorials
Creating Secure Remote Access / A Secure Shell Server
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Learn More
Subtitles of the Movie (Red Hat Certified Engineer / Creating Secure Remote Access / A Secure Shell Server)
The Secure Shell, SSH for short, is one of the services you need to know, at least per the RHCE Exam Prep requirements. SSH supports remote encrypted access to your system. In contrast, remote services such as Telnet and the Remote Shell send passwords over the network in clear text. The Secure Shell encrypts all passwords and all communication between systems. To install the Secure Shell service, you need to install the open ssh server package along with dependencies. The main configuration file is etc slash ssh slash sshd underscore config, and let's open that up; sshd config, and let's set this up for basic operation. First I normally set the protocol 2 directive. The alternative would be to set protocol to comma 1, which allows access by both the current ssh protocol 2, and the less secure ssh protocol 1. I also like to configure a permit route log in directive to no. It's set to yes, by default, in other words, by default the root user can log into the system and if he does so remotely, and a cracker captures the beginning of that communication, it's possible for that cracker to decipher your root password, and that's not what you want. So, I set this to no. Next, I set X11 forwarding to yes. There are a lot of handy Red Hat GUI tools, especially for system administration, and this allows me remote access to those tools. So, let me save these changes and activate the Secure Shell service and make sure the Secure Shell service is set to start in appropriate runlevels. There we go. If you have a Firewall on this system, you'll want to open port 22. It's easily done through the Security Level Configuration tool, and you can do it directly in the Allow Incoming window. This option directly opens port 22. Now that the Secure Shell is started and Firewall access is configured, let's test the Secure Shell service from a remote system. I can log-in to the Secure Shell system using my account name and if etc hosts or dns is properly configured with the host name or a fully qualified domain name of the Secure Shell system. And now, I'm logged in to the secure shell system. Other variations are possible on this command; ssh dash l is equivalent. Obviously if I don't have the host name, I can substitute the IP address assigned to the Secure Shell service. Once this is all confirmed, this opens up a couple of other commands. I could use the SFTP command as a secure FTP client, just substitute SFTP for FTP when you access a remote FTP system, assuming that FTP server is so enabled. There is also a secure copy option where I can copy from a remote or local origin to a local or remote destination. For example, if I wanted to copy a local 1001 dot doc document to the remote system I could specify my log in and then the full path to where I want the file copied. The system asks for my password, and the copy is made.
Tutorial Information
| Course: | Red Hat Certified Engineer |
| Author: | Michael Jang |
| SKU: | 33845 |
| ISBN: | 1-934743-47-X |
| Release Date: | 2008-01-18 |
| Duration: | 6.5 hrs / 94 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
