Home > Articles > Security > Network Security

  • Print
  • + Share This
Like this article? We recommend

Relevant Settings

The information in Table 1 is derived from the actual sshd_conf documentation. If you find something really puzzling, review the documents again. Buy a book. The OpenSSH community is pretty helpful if you have a big problem or worthy suggestion. And don’t forget those hundreds of hits in Safari waiting for you to activate your free trial period.

Table 1 OpenSSH server security settings and possible values.

Directive

Security Importance

Port 22

Running a service on a nonstandard port is part of the "security through obscurity" game, which seldom works with today’s sophisticated scanning engines. Some people have implemented a configuration called "port-knocking," something that requires a separate article. Others ensure that OpenSSH is compiled with TCP wrappers support. This strategy allows for basic address filtering of unwanted hosts. (Want an article on TCP wrappers and what this feature can bring you? Respond below.)

#Protocol 2,1

Protocol 1 seems to have some security risks tied to it. Most sources I read recommend sticking to Protocol 2 for most SSH installations.

# HostKey for protocol version X

See this as a flashing sign. You must protect the integrity of these keys. There is no easy revocation process, and implementing a new key will have lots of SSH clients complaining about the new signature. Your help desk will love you if you keep the updates to organized, communicated changes.

# Lifetime and size of ephemeral version 1 server key

#KeyRegenerationInterval 1h

#ServerKeyBits 768

Still going to use Protocol 1, eh? Right now, 1024 key size seems to be a value that many sources recommended. You must keep track of cryptographic happenings yourself and adjust the key bits up as needed.

# Logging

# obsoletes QuietMode and FascistLogging

#SyslogFacility AUTH

#LogLevel INFO

You must turn on logging. From there, the recommended values get fuzzy. Try the defaults and check the logs. Got enough for an investigation? If not, see the sshd_conf man page for values and their meanings. Servers set to debug levels of logging might indicate that an intruder is analyzing your sshd design closely.

# Authentication:

#LoginGraceTime 2m

#PermitRootLogin yes

#StrictModes yes

#MaxAuthTries 6

These settings generate a lot of discussion among experts. Should you permit a direct login as root? Should you require people to log in with basic accounts and then invoke root privilege as needed? I’m going to invite flames by stating that it’s okay to permit root login under certain conditions (to be listed in any rebuttal to said flames). I also believe that StrictModes is important. If a user opens his or her home directory (o +w), all SSH files are open to hackers—tantamount to loaning your system account to anyone else in the world. StrictModes keeps sshd from accepting logins from poorly secured account settings.

#RSAAuthentication yes

#PubkeyAuthentication yes

#AuthorizedKeysFile .ssh/authorized_keys

RSA authentication is used with Protocol 1 only, so I won’t cover it in this article. PubkeyAuthentication is used to enable public key authentication. Part 1 of this series specifies the potential shortcomings of digital key authentication, but overall I strongly prefer it to passwords—given sane credential handling practices in the field. AuthorizedKeysFile is another important setting. Users can place their public key(s) into a file and thereby enable PubkeyAuthentication. Note the plural: Users can create and misplace and undersecure all the key pairs they choose to use. Your goal is to select a reasonably secure file choice and location for the key pair(s). Something like the /pub directory in /var/ftp might be a bad choice....

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts

#RhostsRSAAuthentication no

# similar for protocol version 2

#HostbasedAuthentication no

Again, RSA authentication is used with Protocol 1 only, and so I’ll duck out of covering it here. Host-based authentication attempts to wed ~/.rhosts or /etc/hosts.equiv with digital key authentication. The default is no, and seemingly for good reason. There are many attacks (and attack tools) that love to attack .rhosts and hosts.equiv. Leave it off.

# Change to yes if you don’t trust ~/.ssh/known_hosts for

# RhostsRSAAuthentication and HostbasedAuthentication

#IgnoreUserKnownHosts no

# Don’t read the user’s ~/.rhosts and ~/.shosts files

#IgnoreRhosts yes

I believe that most users will set home directory permissions to 777 if an attacker asks nicely enough. I believe that they’ll use Yahoo! mail to distribute the most confidential information—and unencrypted at that—if a stranger insinuates a big order. I don’t that believe you should trust user-configured ~/.rhosts or their known_hosts files. I believe that UserKnownHosts and user .rshosts and .shosts should be ignored. Think otherwise? Respond below.

# To disable tunneled clear text passwords, change to no here!

#PasswordAuthentication yes

#PermitEmptyPasswords no

Tough choices, indeed. Passwords suck, but we still use them. They’re configured by users, using predictable values. But until we have easier methods to generate, distribute, and revoke digital keys securely, I think we still need to configure SSH to use passwords. I think you shouldn’t permit empty passwords. Even if you have a service account with a truly secure "forced command," enabling empty passwords will enable it for other users.

# Change to no to disable s/key passwords

#ChallengeResponseAuthentication yes

# Kerberos options

#KerberosAuthentication no

#KerberosOrLocalPasswd yes

#KerberosTicketCleanup yes

#KerberosGetAFSToken no

# GSSAPI options

#GSSAPIAuthentication no

#GSSAPICleanupCredentials yes

#UsePAM no

OpenSSH supports some sophisticated authentication technologies. If your organization uses s/key, Kerberos, or the Generic Security Services Application Program Interface (GSSAPI), test them and then enable them here. PAM is cool; get a book on using it with SSH, however. There’s a lot of complexity, some of which is hinted at strongly in the sshd_conf comments.

#AllowTcpForwarding yes

#GatewayPorts no

Allow forwarding? Provide an open gateway to all? Do you want your sshd to act as a VPN gateway? If you feel you have the skills needed to understand and support/secure such a configuration, enable it. Be prepared to answer for your decision, however.

#UsePrivilegeSeparation yes

Upon successful authentication, sshd forks a process that runs as the user account. Use this setting to slow many privilege-escalation attacks.

#UseDNS yes

I’m going to vote no here. Try it with a yes. If you find that people can’t log in, thank some ISP’s DNS tables. Some don’t have accurate PTR records that resolve successfully to their A records. Even with accurate DNS, what security is provided? I personally believe in authenticating people, not devices and locations. Internet connection-sharing technologies and firewalls that translate outbound traffic to split DNS designs just make it tough to draw too much specific information on a device and its reported IP address.

#PermitTunnel no

See my comments on forwarding. You’re joking, right?

# no default banner path

#Banner /some/path

Security folklore has it that some hacker wasn’t convicted of his/her crimes because of a welcome banner that actually welcomed the users. Anyone have specifics on this? Is it truly important to have a banner that warns users that they’re being monitored? If so, here’s where you specify a banner file.

Clearly, the SSH server has many intricate and useful security settings that can be applied in many ways. Your distribution may have many more—both settings, and ways to apply them. Feel free to plug them into the final row of the table and respond below.

  • + Share This
  • 🔖 Save To Your Account

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