[PATCH] [RHEL/6] logwatch splithosts / hostlimit OVAL checks changes

Jan Lieskovsky jlieskov at redhat.com
Fri Mar 7 15:02:28 UTC 2014


This patch does the following:

    [RHEL/6] logwatch splithosts / hostlimit OVAL checks
    * allow more than just one whitespace after start of new line and
      before HostLimit / SplitHosts directives,
    * allow comments to be present in logwatch config (remove trailing
      $ from patterns),
    * case-insensitively support all of possible values for SplitHosts
      enabled (yes = true = on = 1),
    * case-insensitively support all of possible values for HostLimit
      disabled (no = false = off = 0),
    * update versions and test attestations.

Ad points #1, #2, #3, and #4 -- from /usr/share/logwatch/default.conf/logwatch.conf:
(logwatch defaults conf):

<quote>
# You can put comments anywhere you want to.  They are effective for the
# rest of the line.

# this is in the format of <name> = <value>.  Whitespace at the beginning
# and end of the lines is removed.  Whitespace before and after the = sign
# is removed.  Everything is case *insensitive*.

# Yes = True  = On  = 1
# No  = False = Off = 0
</quote>
  
therefore - allow more than one whitespace at the beginning,
          - allow comments,
          - add (case-insensitive) support for all enabled / disabled value alternatives,
          - update versions & test attestations.

Change tested on RHEL-6 and it seems to be working properly (tested logwatch
runs properly with config value alternatives as detailed above on RHEL-6, and
that the checks return appropriate / expected results).

Please review.

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-RHEL-6-logwatch-splithosts-hostlimit-OVAL-checks.patch
Type: text/x-patch
Size: 4132 bytes
Desc: not available
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20140307/dad42480/attachment.bin>


More information about the scap-security-guide mailing list