Home > Articles > Operating Systems, Server > Solaris

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

Customer Web Site Configuration

The Service Provider grants a certain amount of configuration control to authorized customer administrators. Most of the customers activities are beyond the scope of this article, but we will discuss how the customer configures the web server and updates the web content.

The Service Provider creates one or more administrative accounts for each customer. No such administrative accounts need to run as root, nor are there any files owned by root within their label range. In fact, even if they were given the root password it would do them no good since they are neither authorized to assume the root role, nor to write down to the Admin_Low label. For example, an administrative account for Customer1, created using the SMC Users tool, would have an /etc/user_attr entry like the following:

c1admin::min_label=C1;clearance=C1 HTTP FTP CGI;\
profiles=C1 Rights;

The customer's web configuration files would be owned by c1admin, and maintained at the C1 label; therefore, no privileges would be required for most operations, such as maintaining the web server configuration file, or adding Web users via htpasswd. The C1 Rights profile would be used to start and stop the web server since that will typically require the use of privilege. It should also include the authorization solaris.login.remote for remote access to telnet and ftp. The authorization is listed in the /etc/security/prof_attr entry as follows:

C1 Rights:::Rights for Customer 1 Administrator:\
auths=solaris.login.remote;help=index.html

In addition, an /etc/security/exec_attr entry that includes the apachectl shell script is as follows:

C1 Rights:tsol:cmd:::/usr/apache/bin/apachectl:uid=nobody;\
gid=nobody;clearance=C1 HTTP FTP CGI;label=C1 HTTP FTP;\
privs=proc_owner,net_privaddr

Access to Other Compartments

Since c1admin is cleared for all C1 compartments, he or she can operate at the HTTP FTP or CGI compartments. For example, if c1admin could telnet to c1webserver, the connection would be made at the C1 HTTP FTP label. However, in a hardened environment, remote login could be blocked for that interface by a firewall rule.

The SunScreen™ 3.2 Firewall has been optimized for Trusted Solaris 8 OE, and its ability to block access to specific ports on specific interfaces complements the label-based polices discussed in this article. By default, most trusted services listen for connections at any label from any interface. Therefore, firewall rules should be applied to restrict these services.

A more flexible way to provide access to other compartments is by use of explicit profile entries. For example, a wrapper to switch to the CGI compartment could be done as follows:

#!/bin/sh
# Start a new profile shell
# For clarity, display the current label value in the prompt
PS1='plabel|cut -f2'" " export PS1
/usr/bin/pfsh

If this wrapper is stored as /usr/local/bin/gotoCGI, then the following exec_attr entry provides the c1admin access to the CGI compartment from the C1 label.

C1 Rights:tsol:cmd:::/usr/local/bin/gotoCGI;label=C1 CGI;\
clearance=C1 CGI

Access to the CGI compartment is only available from the C1 label because the clearance specified in such a profile entry must dominate both the current process label and the new label. For example, the c1admin could telnet to c1accounts and successfully use the gotoCGI wrapper, but the wrapper would fail with c1webserver since the default label, C1 HTTP FTP is not dominated by C1 CGI.

Specifying Pathnames for Web Configuration Files

Multilevel Directories (MLDs) are often used in the Trusted Solaris OE to allow processes running at different labels to use the same pathnames when reading and writing data. The real pathname to a file in an MLD is dependent on the label of the process which opens it. By default, Apache looks for its server configuration file in /etc/apache/http.conf. The directory /etc/apache could be converted into an MLD to polyinstantiate a unique instance for each customer. Although this approach is automatic, it is not convenient in this case since each web server runs at a higher label than its configuration file.

It is easier to create unique pathnames for each customer and use MAC to restrict each customer's files to be those processes which dominate the customer's minimum label, e.g., C1. Similarly, the DocumentRoot directory should not be an MLD, either. Instead, the Service Provider should create these directories with the customer's label and ownership. The disjoint labels assigned to directories and files provides strong isolation without the complexity and overhead of using chroot(1M) to create disjoint directories

The path to the configuration file can be explicitly passed to the web server as a command line option, with each customer having a unique pathname for their configuration file which is maintained in a regular directory at a unique label. In our previous article, we discussed how the script /etc/init.d/apache could be modified to provide for labeled execution. Here we make a few more modifications to provide a unique pathname for each customer's server configuration file:

#!/bin/sysh
#
#ident "@(#)apache.sh 1.3 99/11/10 SMI"
#
# extract customer name and profile name from script name
CUSTOMER='basename $0|cut -f2 -d .'
setprof ${CUSTOMER}
CONF_DIR=/home/${CUSTOMER}admin
if [ ! -d ${CONF_DIR} ]; then
  exit 0
fi
# Allow webservers to create entries PID entries in /var/run
setfacl -m group:webserver:rwx /var/run
setfacl -m mask:rws /var/run

The /usr/apache/bin/apachectl file is similarly modified to find the $CONF_DIR using the process label:

# Extract customer name from process label
CUSTOMER='plabel -s|tr -s [:upper:] [:lower:]|\n
cut -d [ -f2|cut -d ' ' -f1'

CONF_DIR=/home/${CUSTOMER}admin
HTTPD="/usr/apache/bin/httpd -f ${CONF_DIR}/http.conf"

For each customer, a hard link to the init.d script is created in /etc/rc3.d based on the customers name, for example:

# ln /etc/init.d/apache /etc/rc3.d/S50apache.c1

Specifying the Security Attributes for the Web Server

The Service Provider is responsible for system security, which includes the maintenance of rights profiles. A rights profile, with a name corresponding to the link's suffix, must be created in which the label, clearance, uid, gid, and privileges (if any) are specified. The contents and format of this profile were discussed in the previous article. In this context, the exec_attr entry to start the Apache web server would look as follows:

c1:tsol:cmd:::/usr/apache/bin/apachectl:uid=nobody;\
gid=webserver;clearance=C1 HTTP FTP CGI;label=C1 HTTP FTP;\
privs=proc_owner,net_privaddr
#
c1:tsol:cmd:::/usr/bin/setfacl:clearance=C1 HTTP FTP CGI;label=C1 HTTP FTP

When using suexec, it is necessary for all the web servers to run with the same user ID that was specified when suexec was compiled. The default value is set to nobody in the Solaris OE distribution. The web server is not privileged to change its user ID, so the Service Provider must specify this value in the rights profile. Furthermore, the web server is not privileged to write to files owned by root, so a common group, webserver, is specified. A group ACL is set on the MLD /var/run in which the web server records its process ID (this ACL is applied at boot time since /var/run is mounted on swap). The logging directory /var/apache/logs uses this group ID as well.

Customer Web Server Configuration

It is the responsibility of the customer to properly configure the web server, but there are no settings that c1admin can choose that will allow access to any other customers, since they are all compartmentalized. Even if the web server is misdirected to the wrong IP address, for example, it won't affect any other customers because the ports on every interface are polyinstantiated. Furthermore, this containment prevents a customer from creating local hyperlinks to another customer's files.

Setting Up Anonymous FTP

Since ftpd is managed by inetd, the server is automatically started with the same label as the requesting client. For anonymous ftp, the setup procedure described in the man page ftpd(1M) is essentially the same in Solaris OE and Trusted Solaris OE. The only additional considerations are that the procedure should be done at the Admin_Low label, and the directory ~ftp/pub should be an MLD. The home directory for ftp should not be an MLD because everything but the contents of the pub directory is the same for all customers, and protected at the Admin_Low label.

  • + 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