The cron.deny file must not have an extended ACL.

From SUSE Linux Enterprise Server v11 for System z Security Technical Implementation Guide

Associated with: CCI-000225

SV-45628r1_rule The cron.deny file must not have an extended ACL.

Vulnerability discussion

If there are excessive file permissions for the cron.deny file, sensitive information could be viewed or edited by unauthorized users.

Check content

Check the permissions of the file. # ls -lL /etc/cron.deny If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.

Fix text

Remove the extended ACL from the file. # setfacl --remove-all /etc/cron.deny

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.