- Background Information
- Security Recommendations
- Securing the System Controller
- Verifying SC Hardening
- Related Resources
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Securing the System Controller
In order to effectively secure an SC, changes are required to both the Solaris OE software running on the SC and the configuration of the Sun Fire 12K or 15K platform. To simplify the Solaris OE installation and deployment of these recommendations, we added customized modules to versions 0.3.8 and later of the Solaris Security Toolkit software. These modules automate the implementation of the security recommendations.
The primary function of the Solaris Security Toolkit software is to automate and simplify building secured Solaris OE systems based on the recommendations contained in this and other security-related Sun BluePrints OnLine articles.
NOTE
We recommend that you disable failover before hardening either of the SCs. Re-enable failover only after both SCs are hardened and tested.
The Sun Fire 12K and 15K SC module sunfire_15k_sc-secure.driver exclusively performs hardening tasks. No minimization of the Solaris OE is performed.
You can use the Sun Fire 12K and 15K SC module of the Solaris Security Toolkit in either standalone or JumpStart_ mode to secure an SC.
NOTE
Configuration modifications for performance enhancements and software configuration are not addressed by the Solaris Security Toolkit.
To harden the SCs, perform the following tasks:
"Adding Security Software" on page 20
"Customizing the Solaris Security Toolkit Driver" on page 26 (optional)
"Overriding Solaris Security Toolkit Defaults" on page 36 (optional)
"Installing Downloaded Software and Implementing Modifications" on page 37
Adding Security Software
The next stage in hardening the SCs requires downloading and installing additional software security packages. This section covers the following tasks:
"Install Solaris Security Toolkit Software" on page 20
"Download Recommended Patch Cluster Software" on page 21
"Download FixModes Software" on page 23
"Download OpenSSH Software" on page 24
"Download the MD5 Software" on page 25
NOTE
Of the software described in this section, the Solaris Security Toolkit, Recommended and Security Patch Cluster, FixModes, and MD5 software are required. Instead of OpenSSH, you can substitute a commercial version of Secure Shell, available from a variety of vendors. You must install a Secure Shell product on the SCs.
Install Solaris Security Toolkit Software
The Solaris Security Toolkit software must be downloaded first, then installed on the SC. Later, you'll use the Solaris Security Toolkit software to automate installing other security software and implementing the Solaris OE modifications for hardening the SC.
The primary function of the Solaris Security Toolkit software is to automate and simplify building secured Solaris OE systems based on the recommendations contained in this and other security-related Sun BluePrints OnLine articles.
NOTE
The following instructions use filenames that are correct only for version 0.3.8 and later of the Solaris Security Toolkit software.
To Download Solaris Security Toolkit Software
Download the latest version of the source file.
At the time of this publication, the version is SUNWjass-0.3.8.pkg.Z. The source file is located at:
Extract the source file into a directory on the server by using the uncompress command:
# uncompress SUNWjass-0.3.8.pkg.Z
Install the Solaris Security Toolkit software onto the server using the pkgadd command:
# pkgadd -d SUNWjass-0.3.8.pkg SUNWjass
Executing this command creates the SUNWjass subdirectory in /opt. This subdirectory contains all Solaris Security Toolkit directories and associated files. The script make-jass-pkg—included in Solaris Security Toolkit software releases since version 0.3—allows administrators to create custom packages using a different installation directory.
Download Recommended Patch Cluster Software
Patches are regularly released by Sun to provide Solaris OE fixes for performance, stability, functionality, and security. It is critical to the security of a system that the most up-to-date patch is installed. To ensure that the latest Solaris OE Recommended and Security Patch Cluster is installed on the SC, this section describes how to download the latest patch cluster.
Downloading the latest patch cluster does not require a SunSolve OnLineSM program support contract.
NOTE
Apply standard best practices to all patch installations. Before installing any patches, evaluate and test them on non-production systems or during scheduled maintenance windows.
To Download Recommended Patch Cluster Software
Download the latest patch from the SunSolve OnLine Web site at:
Click on the Patches link at the top of the left navigation bar.
Select the appropriate Solaris OE version in the Recommended Solaris Patch Clusters box.
In our example, we select Solaris 8 OE.
Select the best download option, either HTTP or FTP, with the associated radio button, then click Go.
A Save As dialog box is displayed in your browser window.
Save the file locally.
Move the file securely to the SC with the scp command, or ftp if Secure Shell is not available.
The scp command used should be similar to the following:
% scp 8_Recommended.zip sun15-sc0:/var/tmp
Move the file to the /opt/SUNWjass/Patches directory and uncompress it as follows:
# cd /opt/SUNWjass/Patches # mv /var/tmp/8_Recommended.zip . # unzip 8_Recommended.zip Archive: 8_Recommended.zip creating: 8_Recommended/ inflating: 8_Recommended/CLUSTER_README inflating: 8_Recommended/copyright inflating: 8_Recommended/install_cluster [. . .]
Later, using the Solaris Security Toolkit software, you will install the patch after downloading all the other security packages.
NOTE
If you do not place the Recommended and Security Patches software into the /opt/SUNWjass/Patches directory, a warning message displays when you execute the Solaris Security Toolkit software.
Download FixModes Software
FixModes is a software package that tightens the default Solaris OE directory and file permissions. Tightening these permissions can significantly improve overall security of the SC. More restrictive permissions make it even more difficult for malicious users to gain privileges on a system.
To Download FixModes Software
Download the FixModes pre-compiled binaries from:
http://www.sun.com/blueprints/tools/FixModes_license.html
The FixModes software is distributed as a precompiled and compressed tar file formatted for systems based on SPARC™ technology. The file name is FixModes.tar.Z.
NOTE
Only certain versions of FixModes are supported for use on Sun Fire SCs. The correct FixModes version must have secure-modes.c version 1.41 and exempt-pkgs.h version 1.1. Newer versions of either file are acceptable. Earlier version of FixModes must not be used to secure Sun Fire SCs.
Once downloaded, move the file securely to the SC with the scp command, or ftp if scp is not available.
The scp command used should be similar to the following command:
% scp FixModes.tar.Z sun15-sc0:/var/tmp
Save the file, FixModes.tar.Z, in the Solaris Security Toolkit Packages directory in /opt/SUNWjass/Packages, with the following commands:
# cd /opt/SUNWjass/Packages # mv /var/tmp/FixModes.tar.Z .
CAUTION
Leave the file in its compressed state.
Later, using the Solaris Security Toolkit software, you'll install the FixModes software after downloading all the other security packages.
Download OpenSSH Software
In any secured environment, the use of encryption in combination with strong authentication is required to protect user-interactive sessions. At a minimum, network access to the SC must be encrypted.
The tool most commonly used to implement encryption is Secure Shell software, whether a version bundled with Solaris, a third-party commercial, or open source (freeware) version. To implement all the security modifications performed by the Solaris Security Toolkit software and recommended in this article, you must implement a Secure Shell software product.
NOTE
With the release of Solaris 9 OE, a version of Solaris Secure Shell is included. If using Solaris 9 OE, we strongly recommend using this Secure Shell version.
Information on where to obtain commercial versions of Secure Shell is provided in "Related Resources" on page 43.
The Solaris Security Toolkit software disables all non-encrypted user-interactive services and daemons on the system, in particular daemons such as in.telnetd and in.ftpd.
Access to the system can be gained with Secure Shell similarly to what is provided by Telnet and ftp.
NOTE
If you choose to use a Secure Shell product other than OpenSSH, install and configure it before or during the Solaris Security Toolkit software run.
To Download OpenSSH Software
NOTE
If the SC is running Solaris 9 OE, you can use the Solaris Secure Shell software and skip the OpenSSH installation steps in this section.
Obtain the following Sun BluePrints online article and use the instructions in the article for downloading the software.
A Sun BluePrints OnLine article about how to compile and deploy OpenSSH titled "Building and Deploying OpenSSH on the Solaris Operating Environment" is available at:
http://www.sun.com/blueprints/0701/openSSH.pdf
Later, using the Solaris Security Toolkit software, you'll install the OpenSSH software after downloading all the other security packages.
CAUTION
Do not compile OpenSSH on the SC and do not install the compilers on the SC. Use a separate Solaris OE system—running the same Solaris OE version, architecture, and mode (for example, Solaris 8 OE, Sun4U, and 64 bit)—to compile OpenSSH. If you implement a commercial version of Secure Shell, then no compiling is required.
Download the MD5 Software
The MD5 software validates MD5 digital fingerprints on the SC. Validating the integrity of Solaris OE binaries provides a robust mechanism to detect system binaries that are altered or trojaned (hidden inside something that appears safe) by unauthorized users. By modifying system binaries, attackers provide themselves with backdoor access onto a system; they hide their presence and cause systems to operate in unstable manners.
To Install the MD5 Software
Download the MD5 binaries from the following web site:
http://www.sun.com/blueprints/tools/md5_license.html
The MD5 programs are distributed as a compressed tar file.
Move the file md5.tar.Z securely to the SC with the scp command, or ftp if scp is not available.
The scp command used should be similar to the following command:
% scp md5.tar.Z sun15-sc0:/var/tmp
Copy the file, md5.tar.Z, to the Solaris Security Toolkit Packages directory in /opt/SUNWjass/Packages.
CAUTION
Do not uncompress the tar archive.
After the MD5 software is saved to the /opt/SUNWjass/Packages directory, the execution of the Solaris Security Toolkit installs the software.
After the MD5 binaries are installed, you can use them to verify the integrity of executables on the system through the Solaris Fingerprint Database. More information on the Solaris fingerprint database is available in the Sun BluePrints OnLine article titled The Solaris™ Fingerprint Database - A Security Tool for Solaris Software and Files.
(Optional) Download and install Solaris Fingerprint Database Companion and Solaris Fingerprint Database Sidekick software from the SunSolve Online web site at:
We strongly recommend that you install these optional tools and use them with the MD5 software. These tools simplify the process of validating system binaries against the database of MD5 checksums. Use these tools frequently to validate the integrity of the Solaris OE binaries and files on the cluster nodes.
These tools are described in the The Solaris™ Fingerprint Database - A Security Tool for Solaris Software and Files article.
Customizing the Solaris Security Toolkit Driver
If you determine that your system requires some of the services and daemons disabled by the Solaris Security Toolkit, or you want to enable any of the inactive scripts available in the Solaris Security Toolkit, do so before executing the Solaris Security Toolkit.
As described earlier in this article, the SMS 1.2 software provides new capabilities for securing the MAN network:
Disable ARP on the MAN network.
Disable all I1 IP traffic between the SCs and specific domains.
Also, you can use Solaris Secure Shell as an alternative transport mechanism for fomd, removing the absolute requirement for in.rshd, in.rlogind, in.rexecd and /.rhosts on the SC. We strongly recommend that you use this alternative transport. To use this functionality with SMS 1.2, patch number 112481-05 or newer must be installed on the SC.
We strongly recommend that you disable ARP on the MAN network. For multi-domain system configurations where domain separation is of critical concern, we also recommend disabling IP connectivity between the SC and those domains that require separation.
Implementing any of these modifications to the SC requires modifying the files included with the Solaris Security Toolkit, as well as domain side modifications when disabling ARP on the MAN network. In addition, if you are implementing Secure Shell as an alternative transport for fomd, then additional manual steps are required.
The following sections provide instructions for using each of these options. The instructions include the required modifications to the Solaris Security Toolkit driver in addition to any manual modifications required. The modifications described are cumulative; if you want to use all three options, perform all the steps described in each of the three sections.
To Disable ARP
To add the necessary features or customize the hardening required for your system, edit a copy of the sunfire_15k_sc-hardening.driver file..
# cd /opt/SUNWjass/Drivers # vi sunfire_15k_sc-hardening.driver
CAUTION
To preserve your changes for future updates and prevent the Solaris Security Toolkit from overriding your changes, modify only a copy of the driver. Keep the original Solaris Security Toolkit driver as a master.
If static ARP configuration is required for this SC, uncomment s15k-static-arp.fin from the driver by removing the # symbol in front of the script.
After editing the line, it should appear as follows in the JASS_SCRIPTS definition:
s15k-static-arp.fin
Review the domain hostname to MAC address mapping in the sms_sc_arp file.
This file is in the /opt/SUNWjass/Files/etc directory. The Solaris Security Toolkit uses the following initial values (sun15-a through sun15-r) in this file:
sun15-a 08:00:20:d5:c6:09 sun15-b 08:00:20:fc:7e:4e sun15-c 08:00:20:b2:a8:c7 sun15-d 08:00:20:cf:ad:7d sun15-e 08:00:20:ce:de:e5 sun15-f 08:00:20:cc:c9:b7 sun15-g 08:00:20:9d:02:e1 sun15-h 08:00:20:2a:7f:f6 sun15-i 08:00:20:f4:39:37 sun15-j 08:00:20:6e:aa:31 sun15-k 08:00:20:90:67:88 sun15-l 08:00:20:ce:e6:5e sun15-m 08:00:20:5a:27:7f sun15-n 08:00:20:55:e5:36 sun15-o 08:00:20:67:78:73 sun15-p 08:00:20:c6:84:b5 sun15-q 08:00:20:c0:37:cb sun15-r 08:00:20:41:9d:68
If your site configuration for the MAN network uses different domain hostnames, replace the sun15-a through sun15-r values with your hostnames.
If your site configuration requires different MAC addresses, replace them with MAC addresses that match your domain hostnames in this file for both SCs.
Review the floating IP Address and matching MAC address of the SC in the sms_domain_arp file.
This file is in the /opt/SUNWjass/Files/etc directory. The Solaris Security Toolkit uses the following initial values in this file:
192.168.103.1 08:00:20:63:49:1e
If your site configuration for the MAN network uses a different floating IP address for the SC, replace the 192.168.103.1 value with your IP floating address.
If your site configuration requires a different MAC address than the initial 08:00:20:63:49:1e value, replace it with the MAC address that matches the floating IP address on all domains and both SCs.
All the domains must use the same /etc/sms_domain_arp file.
CAUTION
The floating IP address in this file must match the IP address chosen as the floating IP address for the SC on the I1 MAN network. Any mismatches will cause MAN network failures. These failures can adversely affect the reliability, availability, and serviceability (RAS) of the platform.
NOTE
If a domain is configured to have both s15k-exclude-domains.fin and s15k-static-arp.fin applied to it, the result is equivalent to s15k-exclude-domains.fin. It is possible, however, to have some domains excluded while others use static ARPs. We strongly recommend that you disable ARP on the I1 MAN network to protect against ARP-spoofing attacks. Note that disabling ARP on the I1 MAN network is a modification that affects the entire chassis and all the domains in the chassis. It is not possible to disable ARP only between certain domains and the SC.
To Disable I1 Traffic
To add the necessary features or customize the hardening required for your system, edit a copy of the sunfire_15k_sc-hardening.driver file..
# cd /opt/SUNWjass/Drivers # vi sunfire_15k_sc-hardening.driver
CAUTION
To preserve your changes for future updates and prevent the Solaris Security Toolkit from overriding your changes, modify only a copy of the driver. Keep the original Solaris Security Toolkit driver as a master.
If domain exclusion is required for this SC, uncomment s15k-exclude-domains.fin from the driver by removing the # symbol in front of the script.
After editing the line, it should appear as follows in the JASS_SCRIPTS definition:
s15k-exclude-domains.fin
The default configuration of the s15k-exclude-domains.fin script is to disable I1 IP connectivity for all possible domains on the system.
If you do not want the default configuration, then edit the s15k-exclude-domains.fin script.
The s15k-exclude-domains.fin script is in the /opt/SUNWjass/Files directory and includes a variable, domain_RE, which specifies the domains to have their I1 IP connectivity disabled. To modify the domains that are impacted by this script, the definition of domain_RE must be changed. For example, if the following regular expression were used, then all domains would have their IP I1 connectivity disabled except for domain D:
domain_RE='D[A-CE-R]-I1'
NOTE
If a domain is configured to have both s15k-exclude-domains.fin and s15k-static-arp.fin applied to it, the result is equivalent to s15k-exclude-domains.fin. It is possible, however, to have some domains excluded while others use static ARPs. We strongly recommend that you disable ARP on the I1 MAN network to protect against ARP-spoofing attacks. Note that disabling ARP on the I1 MAN network is a modification that affects the entire chassis and all the domains in the chassis. It is not possible to disable ARP only between certain domains and the SC.
To Use fomd With Secure Shell Instead of r*
NOTE
We recommend that you disable the failover mechanism before hardening the SCs. Re-enable failover only after you harden and test both SCs.
Using fomd with Secure Shell involves performing the following set up procedures:
"Verify Installation or Install Patch and Secure Shell Software" on page 30
"Configure Secure Shell" on page 31
"Reboot the SCs and Verify Configurations" on page 34
"Add Features and Customize the Hardening" on page 35
Verify Installation or Install Patch and Secure Shell Software
If patch 112481-05 or newer is not installed, download it from SunSolve OnLine and install it on both SCs.
NOTE
This patch is scheduled to be released in August.
Verify that a Secure Shell version is installed, configured, and running appropriately.
NOTE
For fomd to work properly over Secure Shell, it must be possible for root to ssh from one SC to the other SC without requiring a password or command line options.
Configure Secure Shell
If using the Open BSD-based OpenSSH Secure Shell package, perform the following steps to configure Secure Shell properly between the two SCs.
We recommend creating 2048-bit keys using RSA for Secure Shell protocol version 2. Be aware that using 2048-bit keys may introduce a slight performance reduction.
The defaults for OpenSSH on Solaris 8 (2/02) are 1024-bit keys with RSA for protocol version 1, that is, -t rsa1. You must specify -t rsa to get RSA for protocol version 2.
NOTE
The following steps require that you have root access and know the correct hostnames for the SCs on the I2 MAN network. These are the hostnames that SC failover uses; therefore, Secure Shell must be configured properly for SC failover to work.
In the following steps, we use the filename /.ssh/id_rsa for the Secure Shell keys and the default I2 MAN hostnames, sun15-sc0-i2 and sun15-sc1-i2, for the SCs.
If using Solaris 9 OE, change the default Secure Shell configuration to allow root log in on both SCs:
On both SC0 and SC1, edit the file /etc/ssh/sshd_config to allow root log in.
SC failover does not work if this step is omitted.
Change the PermitRootLogin parameter from no to yes.
Reboot the SCs or restart the Secure Shell server to implement the changes.
On the main SC (SC0) in a terminal window command line, perform the following steps:
NOTE
We recommend that you display terminal windows side by side for both SCs (main and spare) throughout this procedure. Doing so makes it easier to enter the data and perform sequential steps on each SC.
Generate a host key by entering the following command:
# /opt/OBSDssh/bin/ssh-keygen -b 2048 -t rsa
Accept the default filename without entering a pass phrase.
Transfer the public key file to a temporary file on SC1 using either scp (if available) or rcp:
# scp /.ssh/id_rsa.pub sun15-sc1-i2:/.ssh/id_rsa.pub-sc0
or
# rcp /.ssh/id_rsa.pub sun15-sc1-i2:/.ssh/id_rsa.pub-sc0
CAUTION
Do not omit the remote filename or use /.ssh/id_rsa.pub as the filename on SC1. If there is already a public key file on SC1, it may be overwritten and invalidate SC1's private key.
On the spare SC (SC1) in a terminal window command line, perform the following steps:
Generate a host key by entering the following command:
# /opt/OBSDssh/bin/ssh-keygen -b 2048 -t rsa
Accept the default filename without entering a pass phrase.
Transfer the public key file to a temporary file on SC0 using either scp (if available) or rcp:
# scp /.ssh/id_rsa.pub sun15-sc0-i2:/.ssh/id_rsa.pub-sc1
or
# rcp /.ssh/id_rsa.pub sun15-sc0-i2:/.ssh/id_rsa.pub-sc1
CAUTION
Do not omit the remote filename or use /.ssh/id_rsa.pub as the filename on SC0. If there is already a public key file on SC0, it may be overwritten and invalidate SC0's private key.
Return to the main SC and perform the following steps:
Append SC1's public key to the /.ssh/authorized_keys2 or /.ssh/authorized_keys file.
NOTE
If you are using OpenSSH, the file to use is /.ssh/authorized_keys2. If you are using Sun's Secure Shell on Solaris 9, the file to use is /.ssh/authorized_keys. This command creates the file if it does not exist.
# cat /.ssh/id_rsa.pub-sc1 >> /.ssh/authorized_keys2
or
# cat /.ssh/id_rsa.pub-sc1 >> /.ssh/authorized_keys
Remove the temporary file.
# rm /.ssh/id_rsa.pub-sc1
Return to the spare SC and perform the following steps:
Append SC0's public key to the /.ssh/authorized_keys2 or /.ssh/authorized_keys file.
# cat /.ssh/id_rsa.pub-sc0 >> /.ssh/authorized_keys2
or
# cat /.ssh/id_rsa.pub-sc0 >> /.ssh/authorized_keys
Remove the temporary file.
# rm /.ssh/id_rsa.pub-sc0
Due to a known incompatibility between the SMS software and Secure Shell startup script, move the Secure Shell startup script from UNIX run-level 3 to run-level 2 on both the main and spare SC.
# mv /etc/rc3.d/S*ssh* /etc/rc2.d/.
Reboot the SCs and Verify Configurations
Reboot each of the SCs by entering the following command from the platform shell:
# reboot -y
NOTE
You can reboot the SCs while the domains are running.
Verify the configuration on SC0 works properly.
Log into SC1 from SC0 using ssh:
# ssh sun15-sc1-i2
When prompted to add this host to the list of known hosts, answer yes.
Log out of SC1 with "exit."
Log into SC1 from SC0 again with ssh, and verify that no prompts are generated and that the login without a password is successful.
Verify the configuration on SC1 works properly.
Log into SC0 from SC1 using ssh:
# ssh sun15-sc0-i2
When prompted to add this host to the list of known hosts, answer yes.
Log out of SC0 with "exit."
Log into SC0 from SC1 again with ssh, and verify that no prompts are generated and that the login without a password is successful.
Add Features and Customize the Hardening
To add necessary features and customize the hardening required for your system, edit a copy of the sunfire_15k_sc-hardening.driver file..
# cd /opt/SUNWjass/Drivers # vi sunfire_15k_sc-hardening.driver
CAUTION
To preserve your changes for future updates and prevent the Solaris Security Toolkit from overriding your changes, modify only a copy of the driver. Keep the original Solaris Security Toolkit driver as a master.
Uncomment the s15k-sms-secure-failover.fin from the driver by removing the # symbol in front of the script.
After editing the line, it should appear as follows in the JASS_SCRIPTS definition:
s15k-sms-secure-failover.fin
This script disables the r* services in the /etc/inetd.conf file automatically and removes the /.rhosts file. The five services disabled are as follows:
#shell stream tcp nowait root /usr/sbin/in.rshd in.rshd #shell stream tcp6 nowait root /usr/sbin/in.rshd in.rshd #login stream tcp6 nowait root /usr/sbin/in.rlogind in.rlogind #exec stream tcp nowait root /usr/sbin/in.rexecd in.rexecd #exec stream tcp6 nowait root /usr/sbin/in.rexecd in.rexecd
Overriding Solaris Security Toolkit Defaults
If there are some services that must remain enabled, and the Solaris Security Toolkit automatically disables them, you can override the defaults before executing the driver.
To prevent the toolkit from disabling a service, comment out the call to the appropriate finish script in the driver.
For example, if your environment requires Network File System (NFS)-based services, you can leave them enabled. Comment out the disable-nfs-server.fin and disable-rpc.fin scripts by appending a # sign before them in the copy of the sunfire_15k_domain-hardening.driver script.
For more information about editing and creating driver scripts, refer to the Sun BluePrints OnLine article titled "The Solaris™ Security Toolkit - Installation, Configuration, and Usage Guide: Updated for version 0.3."
Installing Downloaded Software and Implementing Modifications
The Solaris Security Toolkit version 0.3.8 and later provides a driver (sunfire_15k_sc-secure.driver) for automating the installation of security software and Solaris OE modifications. The driver performs the following tasks:
Installs and executes the FixModes software to tighten file system permission
Installs the MD5 software
Installs the Recommended and Security Patch Cluster software
Implements almost 100 Solaris OE security modifications
NOTE
The actions performed by each of the scripts is described in the Sun BluePrints OnLine article "The Solaris Security Toolkit - Internals: Updated for version 0.3."
During the installation and modifications implemented in this section, all non-encrypted access mechanisms to the SC —such as Telnet and FTP—are disabled. The hardening steps do not disable console serial access over SC serial ports.
To Install Downloaded Software and Implement Changes
Execute the sunfire_15k_sc-secure.driver script as follows:
# cd /opt/SUNWjass # ./jass-execute -d sunfire_15k_sc-secure.driver ./jass-execute: NOTICE: Executing driver, sunfire_15k_sc-secure.driver ============================================================ sunfire_15k_sc-secure.driver: Driver started. ============================================================ [...]
NOTE
The hardening described in this article is performed in standalone mode, not JumpStart mode, because the SC was built using an interactive Solaris OE installation. For details on the differences between standalone mode and JumpStart mode, refer to the Solaris Security Toolkit documentation.
To View the Contents of the Driver File
To view the contents of the driver file and obtain information about the Solaris OE modifications, refer to the Solaris Security Toolkit documentation available either in the /opt/SUNWjass/Documentation directory or through the web at:
http://www.sun.com/security/jass
For information about other scripts in the Solaris Security Toolkit software, refer to the Sun BluePrints OnLine article titled "Solaris Security Toolkit Internals: Updated for Version 0.3."
To Undo a Solaris Security Toolkit Run
Each Solaris Security Toolkit run creates a run directory in /var/opt/SUNWjass/run. The names of these directories are based on the date and time the run is initiated. In addition to displaying the output to the console, the Solaris Security Toolkit software creates a log file in the /var/opt/SUNWjass/run directory.
CAUTION
Do not modify the contents of the /var/opt/SUNWjass/run directories under any circumstances. Modifying the files can corrupt the contents and cause unexpected errors when you use Solaris Security Toolkit software features such as undo.
The files stored in the /var/opt/SUNWjass/run directory track modifications performed on the system and enable the jass-execute undo feature.
To undo a run or series of runs, use the jass-execute -u command.
For example, on a system where two separate Solaris Security Toolkit runs are performed, you could undo them by using the following command and options:
# pwd /opt/SUNWjass # ./jass-execute -u Please select from one of these backups to restore to 1. September 25, 2001 at 06:28:12 (/var/opt/SUNWjass/run/20010925062812) 2. April 10, 2002 at 19:04:36 (/var/opt/SUNWjass/run/20020410190436) 3. Restore from all of them Choice? 3 ./jass-execute: NOTICE: Restoring to previous run //var/opt/SUNWjass/run/20020410190436 ============================================================ undo.driver: Driver started. ============================================================ [...]
Refer to the Solaris Security Toolkit documentation for details on the capabilities and options available in the jass-execute command.
NOTE
You cannot use the undo feature on install-fixmodes.fin, install-openssh.fin, and install-strong-permissions.fin Solaris Security Toolkit scripts. Refer to the Solaris Security Toolkit documentation for additional information.