Scribd
Upload
30 views

2 - System-Wide Configuration 2.1 - Installing and Maintaining Software

The document discusses recommendations for initial system installation and software updates. It recommends creating separate partitions for /var, /tmp, and optionally /var/log and /home during disk partitioning. It also recommends setting a boot loader password, disabling DHCP for network configuration, choosing a strong root password, and pruning unnecessary software packages. After installation, it recommends enabling the firewall, leaving SELinux in enforcing mode, and updating software regularly using yum or graphical package managers.

Uploaded by

Fantasytrend
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
30 views

2 - System-Wide Configuration 2.1 - Installing and Maintaining Software

The document discusses recommendations for initial system installation and software updates. It recommends creating separate partitions for /var, /tmp, and optionally /var/log and /home during disk partitioning. It also recommends setting a boot loader password, disabling DHCP for network configuration, choosing a strong root password, and pruning unnecessary software packages. After installation, it recommends enabling the firewall, leaving SELinux in enforcing mode, and updating software regularly using yum or graphical package managers.

Uploaded by

Fantasytrend
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

2 - System-wide Configuration

2.1 - Installing and Maintaining Software


The following sections contain information on security-relevant choices during the
initial operating system installation process and the setup of software updates.
2.1.1 - Initial Installation Recommendations
The recommendations here apply to a clean installation of the system, where any
previous installations are wiped out. The sections presented here are in the same
order that the installer presents, but only installation choices with security
implications are covered. Many of the configuration choices presented here can
also be applied after the system is installed. The choices can also be automatically
applied via Kickstart files, as covered in [8].
2.1.1.1 - Disk Partitioning
If using any of the default layouts, check the box to Review and modify
partitioning. The default layout does not create separate partitions or logical
volumes for /var and /tmp. Add logical volumes or partitions for at least /var and
/tmp. Adding logical volumes or partitions for /var/log and /var/log/audit may also
be necessary, depending on system requirements. (See Section 2.6 for more
information about logging and auditing). If user home directories will be stored
locally, create a separate partition for /home as well. If creating a custom layout,
create the partitions mentioned in the previous paragraph, as well as separate ones
for /, /boot and swap space. You may need to make the / logical volume smaller to
create space for the additional partitions.
2.1.1.2 - Boot Loader Configuration
Check the box to Use a boot loader password and create a password. Once this
password is set, anyone who wishes to change the boot loader configuration will
need to enter it. More information is available in Section 2.3.5.2. Assigning a boot
loader password prevents a local user with physical access from altering the boot
loader configuration at system startup.
2.1.1.3 - Network Devices
The default network device configuration uses DHCP, which is not recommended.
Unless use of DHCP is absolutely necessary, click the Edit button and: *
Uncheck Use Dynamic IP configuration (DHCP). * Uncheck Enable IPv4
Support if the system does not require IPv4. (This is uncommon.) * Uncheck
Enable IPv6 Support if the system does not require IPv6. * Enter appropriate
IPv4 and IPv6 addresses and prefixes as required. With the DHCP setting disabled,
the hostname, gateway, and DNS servers should then be assigned on the main
screen. Sections 3.9.1 and 3.9.2 contain more information on network
configuration and the use of DHCP.
2.1.1.4 - Root Password
The security of the entire system depends on the strength of the root password. The
password should be at least 12 characters long, and should include a mix of
capitalized and lowercase letters, special characters, and numbers. It should also
not be based on any dictionary word.
2.1.1.5 - Software Packages
Uncheck all package groups, including the package groups Software
Development and Web Server, unless there is a specific requirement to install
software using the system installer. If the machine will be used as a web server, it
is preferable to manually install the necessary RPMs instead of installing the full
Web Server package group. See Section 3.16 for installation and configuration
details. Use the Customize now radio box to prune package groups as much as
possible. This brings up a two-column view of categories and package groups. If
appropriate, uncheck X Window System in the Base System category to avoid
installing X entirely. Any other package groups not necessary for system operation
should also be unchecked. Much finer-grained package selection is possible via
Kickstart as described in [8].
2.1.1.6 - First-boot Configuration
The system presents more configuration options during the first boot after
installation. For the screens listed, implement the security-related
recommendations: Screen Recommendation Firewall Leave set to Enabled. Only
check the Trusted Services that this system needs to serve. Uncheck the default
selection of SSH if the system does not need to serve SSH. SELinux Leave
SELinux set to Enforcing mode. Kdump Leave Kdump off unless the feature is
required, such as for kernel development and testing. Screen Recommendation Set
Up Software Updates If the system is connected to the Internet now, click Yes,
Id like to register now. This will require a connection to either the Red Hat
Network servers or their proxies or satellites. This can also be configured later as
described in Section 2.1.2.1. Create User If the system will require a local user
account, it can be created here. Even if the system will be using a network-wide
authentication system as described in Section 2.3.6, do not click on the Use
Network Login... button. Manually applying configuration later is preferable.
2.1.2 - Updating Software
The yum command line tool is used to install and update software packages. Yum
replaces the up2date utility used in previous system releases. The system also
provides two graphical package managers, pirut and pup. The pirut tool is a
graphical front-end for yum that allows users to install and update packages while
pup is a simple update tool for packages that are already installed. In the
Applications menu, pirut is labeled Add/Remove Software and pup is labeled
Software Updater. It is recommended that these tools be used to keep systems up to
date with the latest security patches.

You might also like