
Chapter 7. Security and Authentication
26
• Run slaptest to check the validity of the configuration file and specify the new configuration
directory:
slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d
• Configure permissions on the new directory:
chown -R ldap:ldap /etc/openldap/slapd.d
chmod -R 000 /etc/openldap/slapd.d
chmod -R u+rwX /etc/openldap/slapd.d
• Once the service is confirmed to be working in the new configuration directory, remove the old
configuration file:
rm -rf /etc/openldap/slapd.conf
7.4. Checksums
Red Hat Enterprise Linux now uses the SHA-256 digest algorithm for data verification and
authentication in more places than before, upgrading from the cryptographically weaker SHA-1 and
MD5 algorithms.
7.5. Pluggable Authentication Modules (PAM)
Common configuration for PAM services is located in the /etc/pam.d/system-auth-ac file.
Authentication modules are now also written into additional PAM configuration files: /etc/pam.d/
password-auth-ac, etc/pam.d/smartcard-auth-ac and /etc/pam.d/fingerprint-
auth-ac.
The PAM module for sshd and other remote services such as ftpd now include the /etc/pam.d/
password-auth file in Red Hat Enterprise Linux 6 instead of /etc/pam.d/system-auth.
7.6. System Users
The threshold for statically assigned UID/GID numbers (defined by the setup package in the /usr/
share/doc/setup-*/uidgid file) has increased from 100 (in Red Hat Enterprise Linux 3, 4, and 5)
to 200 in Red Hat Enterprise Linux 6. This change can affect systems that have 100-200 dynamically
or statically assigned UID/GIDs, and cause failure in the installation and running of some appications.
Dynamic UID/GID allocation now ranges from 499 downward in Red Hat Enterprise Linux 6. For static
system user creation without reservations enforced by the setup package, it is recommended to use
the UID/GID area of 300 and above.
Komentarze do niniejszej Instrukcji