From Fedora Project Wiki
(initial set of proposed criteria, done up in the current stylee (still missing one, saving to avoid data loss))
 
(add post-install requirements header)
Line 1: Line 1:
{{anchor|post-install-requirements}}
=== <span style="text-decoration:underline">Post-install requirements</span> ===
{{anchor|system-log-forwarding}}
{{anchor|system-log-forwarding}}
==== System log forwarding ====
==== System log forwarding ====

Revision as of 00:07, 12 June 2014

Post-install requirements

System log forwarding

It must be possible to forward system logs from one system running the release to another using rsyslog.

Details

This criterion assumes a working network connection between the machines, appropriate firewall configuration, and a fairly straightforward rsyslog configuration. A more exotic configuration failing is unlikely to be considered a violation of this criterion.

References

Firewall configuration

After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly.

Install time configuration

To explain the last part of this criterion - it is possible to include firewall configuration options in a kickstart-driven installation, and the criterion requires that those options work as expected. The options considered to be 'supported' are those documented at Anaconda/Kickstart#firewall. Should kickstart firewall options conflict with the settings that would otherwise result from a deployed server role, the kickstart options must take precedence.

References

SELinux configuration

Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode.

References