Home > Articles > Security > Software Security

📄 Contents

  1. Why Not RSH?
  2. SSH: The "Ssafer" Alternative
  3. Conclusion
  4. Resources
Like this article? We recommend

SSH: The "Ssafer" Alternative

SSH provides all the functionality of rsh, rcp, and rlogin, and does so in a much safer manner. There are two versions of the SSH protocol, appropriately called SSH1 and SSH2. SSH1 has some inherent security issues of its own, so SSH2 is the version to consider. For this discussion, we'll use the terms SSH and SSH2 interchangeably.

SSH provides a secure environment by encrypting network traffic between hosts. To do this, SSH relies on the principle of public key cryptography.

NOTE

In public key cryptography, a pair of encryption keys is used to encrypt and decrypt messages. One key is public, and the other private. A host's public key can be used to encrypt messages to that host. Only the matching private key can be used to decrypt those messages. So long as the private key is not compromised, messages encrypted with the public key can only be decrypted by the intended recipient.

By encrypting traffic, SSH helps to prevent man-in-the-middle attacks, and makes it far more difficult for hackers to "listen in" on your session. Pretend for a moment that someone has gained root access to one of the hosts on your network. You log into that server, and from there log into a remote server and su to root. If you're using RSH, the bad guy can easily sniff clear-text traffic and get the root password for that remote server. But if you're using SSH, that password you just sent is encrypted before it reaches the intruder's prying eyes, and can only be decrypted by someone with access to the private key stored on the remote server. Although SSH won't prevent every security breach, it can certainly minimize the damage when a breach occurs.

Migrating Users from RSH to SSH

From the user's perspective, switching from RSH to SSH can be as easy as using s instead of r when running commands. The commands ssh, scp, and slogin can easily double for rsh, rcp, and rlogin after the environment has been set up.

TIP

If users are exceptionally resistant to change, just symlink the r* commands to their s* equivalents when you're ready to migrate everything.

To migrate users from RSH to SSH, a bit of preparation is needed. The first step is to set up the SSH daemon on every host. Your operating system vendor likely provides an SSH server daemon suitable for use on your systems; if not, OpenSSH offers versions of SSH for pretty much every *nix system out there. (They also offer an SSH FAQ and man pages for all the SSH commands.) The installation of sshd is pretty straightforward; you'll probably spend the most time on the configuration file. Have a look at the sshd_config man page before you begin, and chart out the options you want to use.

As part of the sshd installation process, you'll be generating a public/private key pair for the host. After you have sshd up and running on all your hosts, gather all the public host keys into a single file and load it on each host. This file is saved as /etc/ssh/ssh_known_hosts. Each time a user connects to another host, SSH checks this file for that host's public key, and the connection request sent is encrypted using this key. The public key for the user is then passed to the remote host. All traffic sent back from the remote host is encrypted with the user's public key.

NOTE

Public keys for hosts can also be stored in ~/.ssh/known_hosts. When a user connects to another system via SSH, if that host's public key is not found on the client system the user will be warned that the remote host's identity has not been verified. The user then has the option of adding the host to the known_hosts file, or canceling the connection.

SSH's private key encryption protects users against DNS hijacking attacks. Even if an attacker can hijack a server's traffic (and even return the appropriate public key when users try to log in), he won't be able to decrypt the SSH traffic sent from the client because he doesn't have the appropriate private host key. By maintaining an up-to-date version of the /etc/ssh/ssh_known_hosts file on all hosts, and educating your users about host-key warnings, you can verify the identity of any host on your network each time you connect.

The next step is to set up keys for all users to mimic rsh functionality. There are also some choices to be made regarding the level of security required for your environment. Although I hope you'll choose to go with the most secure configuration available, any of the SSH options are more secure than plain RSH.

Security Levels

Level

Description

Minimal Security

Host-based authentication via /etc/ssh_host_rsa_key file. The only real advantage this security level offers over rsh is the encryption of all traffic between hosts.

Better Security

One key pair generated for each user and distributed to all hosts. If you choose this route, keep in mind that if an account is compromised on one host, it will been compromised on every host.

Best Security

Key pair generated for every user on every host. Creating a different key for each host requires the most work, but it offers the greatest security.


For added security, you can require each user to enter a passphrase before his or her private key can be accessed. If you choose this method, you must add ssh-agent to the appropriate profile files for your shells (such as /etc/profile or ~/.profile for Bourne, or /etc/bashrc or ~/.bashrc for Bash). ssh-agent runs when a user logs in, and manages the user's access to his or her private keys.

If you serve up home directories via NFS, there are some additional considerations. If the private key is stored in an NFS home directory, the contents of each user's private key file will be transmitted in the clear every time he or she logs in. One solution that protects against this possibility is to set up a directory just for SSH keys under a local filesystem on each host, and link the ~/.ssh NFS directory to a corresponding local user directory:

[/NFS/home/rhunter] $ ls –l .ssh
lrwxr-xr-x 1 rhunter rhunter 25 8 Dec 03:05 .ssh -> /LocalFS/rhunter/.ssh/
[/NFS/home/rhunter] $ ls –ld /LocalFS/rhunter/.ssh
drwx------ 5 rhunter rhunter 170 4 Dec 04:35 /LocalFS/rhunter/.ssh/

You'll also want to modify the AuthorizedKeysFile directive in your sshd_config file:

AuthorizedKeysFile /LocalFS/%u/.ssh

Be sure that permissions are set correctly on these items:

  • Directory: 700

  • Private key: 600

  • Public key: 644

As for generating the user keys themselves, the best solution probably depends on your environment and user level. You can inform users of the change to SSH, and give them a script to run that calls ssh-keygen with the appropriate switches. The script can then use an automated process to move the keys out to other hosts, or notify you that the keys are ready to be moved. If users require a greater level of hand-holding, you could script a process that will su to each user account, generate key pairs for that user, copy the public keys to a central repository, and distribute the public keys to all hosts. Either way, once the keys are in place, users will be able to ssh with little or no greater effort than rsh requires today.

After users have been migrated from RSH to SSH, the last big hurdle is dealing with automated processes that might use RSH. Migrating these processes to SSH isn't hard once you identify them, but making sure that you've caught all of them before you disable RSH is critical. After you've dealt with the known processes, the safest approach is to sniff for RSH traffic on your network for a week or so. Ideally, you won't see any RSH connections at this point. But if you do, it should be fairly easy to look at the traffic and identify the owner, source, destination, and purpose. Work with the owner of the process to migrate to SSH. Once you're confident that you've dealt with all your rsh traffic, disable rshd on all hosts. For added protection, you can block traffic to port 514 on your firewalls and routers.

Congratulations! You're now RSH-free!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020