Home > Articles > Programming > General Programming/Other Languages

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

Solaris OE Service Restriction

The typical hardening of a Solaris OE system involves commenting out all of the services in the /etc/inetd.conf file and disabling unneeded system daemons from starting. All of the interactive services normally started from inetd are then replaced by Secure Shell (SSH). Unfortunately, Sun Cluster 3.0 12/01 software does not permit the entire contents of the /etc/inetd.conf file to be commented out. The primary reason for this limitation is that volume management software requires several RPC services to be available. The Sun Cluster 3.0 12/01 software also installs additional RPC- based services. These Sun Cluster software-specific RPC services include the rpc.pmfd and rpc.fed services.

The security recommendations in this article include all Solaris OE modifications that do not impact required Sun Cluster 3.0 node functionality. This does not mean that these modifications are appropriate for every node. In fact, it is likely that some of the services disabled by the default suncluster30u2-secure.driver script will affect some applications. Because applications and their service requirements vary, it is unusual for one configuration to work for all applications.


Consider the role of a secured configuration in the context of the applications and services that the Sun Cluster 3.0 12/01 software will support. The security configuration presented in this article is a high-watermark for system security, as every service that is not required by the Sun Cluster 3.0 12/01 software and agents is disabled. This information should provide you with a clear idea of which services can and cannot be disabled without affecting the behavior of the Sun Cluster 3.0 12/01 software and the three agents.

For information about Solaris OE services and for recommendations about mitigating their security implications, refer to the Sun BluePrints OnLine article "Solaris™ Operating Environment Security: Updated for the Solaris 8 Operating Environment" and the Sun BluePrints OnLine article "Solaris™ Operating Environment Network Settings for Security: Updated for Solaris 8 Operating Environment." The recommendations in these articles are implemented with the Solaris Security Toolkit software in standalone and JumpStart modes. In addition, the Sun BluePrints OnLine article "The Solaris™ Security Toolkit - Internals: Updated for version 0.3" describes the functions of each of the toolkit scripts. The following section summarizes the modifications made by the toolkit during a Sun Cluster 3.0 12/01 software hardening run.

Hardening Modifications

Each of the modifications performed by the toolkit to harden Sun Cluster 3.0 nodes falls into one of the following categories:

  • Disable
  • Enable
  • Install
  • Remove
  • Set
  • Update

In addition, the toolkit copies files from the toolkit distribution to increase the security of the system. These system configuration files change the default behavior of syslogd, system network parameters, and a variety of other system configurations.

The following sections describe each of these categories and the scripts modifications they perform. For a complete listing of the scripts included in the suncluster30u2-secure.driver refer to the Solaris Security Toolkit Drivers directory.

Disable Scripts

These scripts disable services on the system. Disabled services include the NFS client and server, the automounter, the DHCP server, printing services, and the window manager. The goal of these scripts is to disable all of the services that are not required by the system.

A total of 30 disable scripts are included with the Sun Cluster 3.0 12/01 software-hardening driver. These scripts impose modifications to disable all, or part, of the following services and configuration files:










core generation


















Enable Scripts

These scripts enable the security features that are disabled by default on Solaris OE. These modifications include:

  • Enabling optional logging for syslogd and inetd

  • Requiring NFS client requests to use privileged ports for all requests

  • Enabling process accounting

  • Enabling improved sequence number generation per RFC 1948

  • Enabling optional stack protection and logging to protect against most buffer overflow attacks

While some of these services are disabled, their optional security features remain enabled so that they are used securely if enabled in the future.

Install Scripts

These scripts create new files to enhance system security. In the Sun Cluster 3.0 driver, the following Solaris OE files are created to enhance the security of the system:

  • An empty /etc/cron.d/at.allow to restrict access to at commands

  • An updated /etc/ftpusers file with all system accounts to restrict system FTP access

  • An empty /var/adm/loginlog to log unsuccessful login attempts

  • An updated /etc/shells file to limit which shells can be used by system users

  • An empty /var/adm/sulog to log su attempts

In addition to creating the preceding files, some install scripts also add software to the system. Specifically, for the Sun Cluster 3.0 nodes, the following software is installed:

  • Recommended and Security patch clusters

  • MD5 software

  • FixModes software

Remove Scripts

Only one remove script is distributed with the Sun Cluster 3.0 driver and it used to remove unused Solaris OE system accounts. The accounts that are removed are no longer used by the Solaris OE and can safely be removed. The accounts that are removed include:

  • smtp
  • nuucp
  • listen
  • nobody4

Set Scripts

These scripts configure the security features of the Solaris OE that are not defined by default. Fourteen of these scripts are distributed with the Sun Cluster 3.0 driver and they can configure the following Solaris OE security features not enabled by default:

  • root password
  • ftpd banner
  • telnetd banner
  • ftpd UMASK
  • login RETRIES
  • power restrictions
  • system suspend options
  • TMPFS size
  • user password requirements
  • user UMASK

Update Scripts

These scripts update the configuration files that are shipped with the Solaris OE but do not have all of their security settings properly set. The following configuration files are modified:

  • at.deny
  • cron.allow
  • cron.deny
  • logchecker
  • inetd.conf

Hardening Results

After hardening, the following non-cluster services remain running on a node:

# ps -ef | grep -v cluster
root   0   0 0  Oct 25 ?    0:01 sched
root   1   0 0  Oct 25 ?    0:00 /etc/init -
root   2   0 0  Oct 25 ?    0:00 pageout
root   3   0 0  Oct 25 ?    4:41 fsflush
root  466  1 0  Oct 25 ?    0:00 /usr/lib/saf/sac -t 300
root  65   1 0  Oct 25 ?    0:01 /usr/lib/sysevent/syseventd
root  67   1 0  Oct 25 ?    0:00 /usr/lib/sysevent/syseventconfd
root  77   1 0  Oct 25 ?    8:22 devfsadmd
root  265   1 0  Oct 25 ?    0:00 /usr/lib/netsvc/yp/ypbind -broadcast
root  252   1 0  Oct 25 ?    0:00 /usr/sbin/rpcbind
root  167   1 0  Oct 25 ?    0:00 /usr/sbin/in.rdisc -s
root  469  466 0  Oct 25 ?    0:00 /usr/lib/saf/ttymon
root  255   1 0  Oct 25 ?    0:00 /usr/sbin/keyserv -d
root  394   1 0  Oct 25 ?    0:00 /usr/lib/utmpd
root  274   1 0  Oct 25 ?    0:00 /usr/sbin/inetd -s -t
root  318   1 0  Oct 25 ?    0:00 /usr/lib/inet/xntpd
root  285   1 0  Oct 25 ?    0:00 /usr/sbin/syslogd -t
root  327  274 0  Oct 25 ?    0:00 rpc.metad
root  396   1 0  Oct 25 ?    0:00 /usr/sbin/nscd
root  373   1 0  Oct 25 ?    0:00 /usr/sbin/cron
root  391   1 0  Oct 25 ?    0:00 /usr/sbin/vold
root  470   1 0  Oct 25 ?    0:00 /usr/lib/sendmail -q15m
root 1060   1 0 13:54:45 ?    0:00 /opt/OBSDssh/sbin/prngd --cmdfile /etc/prngd.conf --seedfile 
  root 1086   1 1 13:55:00 ?    0:00 /opt/OBSDssh/sbin/sshd

The preceding listing of services may not exactly match your environment. Several configuration modifications were made on this node after the OS was installed. These modifications included the configuration of xntp, NIS, and the installation of OpenSSH.

The following output was generated by nmap, a popular freeware security scanning tool:

# nmap -p 1-65535

Starting nmap V. 2.53 by fyodor@insecure.org ( http://www.insecure.org/nmap/ )
Port      State    Service
22/tcp    open    ssh           
111/tcp   open    sunrpc         
8059/tcp  open    unknown         
8060/tcp  open    unknown         
32785/tcp open    unknown         
32786/tcp open    sometimes-rpc25     
32787/tcp open    sometimes-rpc27     
32788/tcp open    unknown         
32789/tcp open    unknown         
32790/tcp open    unknown         
32791/tcp open    unknown         
32804/tcp open    unknown         
32806/tcp open    unknown         
32811/tcp open    unknown         
32821/tcp open    unknown         

Nmap run completed -- 1 IP address (1 host up) scanned in 211 seconds

Ports 8059 and 8060 are Sun Cluster 3.0 software-specific ports that accept only connections from other cluster nodes. When a connection request from a non-cluster node is received, the following message is logged to syslog:

Oct 30 14:00:52 phys-sps-1 cl™runtime: WARNING: Received a connect request from a node 
not configured in the cluster. Nodeid 0 ipaddr 0x8194b556

Monitor log files for these types of messages so that appropriate action can be taken when unauthorized access attempts are made against the cluster.

Cluster nodes are added based on the authentication method defined in the Sun Cluster 3.0 12/01 software configuration. It is strongly recommended that you use the strongest possible method of authentication. The available options are discussed in the Node Authentication section 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.


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.


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.


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.


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


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


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.


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.


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