Bug 1295886

Summary: logwatch --service sshd --detail 8 does not print Kerberos summary
Product: Red Hat Enterprise Linux 6 Reporter: Martin Frodl <mfrodl>
Component: logwatchAssignee: Jan Synacek <jsynacek>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: bnater
Target Milestone: rcKeywords: EasyFix, FastFix, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: logwatch-7.3.6-55.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1295888 (view as bug list) Environment:
Last Closed: 2017-03-21 09:32:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1356047, 1359260    

Description Martin Frodl 2016-01-05 17:16:14 UTC
Description of problem:

When called with --service sshd --detail 8, logwatch does not print out the summary of successful Kerberos authentications. This summary is printed with detail level 9, 10, but also 7. Thus the detail level of 8 may be less verbose than 7, which is clearly undesired.

The root cause of this behaviour seems to be in using the 'greater than' operator where a 'greater than or equal' should be (in /usr/share/logwatch/scripts/services/sshd):

--- sshd.orig	2016-01-05 12:09:26.153006890 -0500
+++ sshd	2016-01-05 12:12:09.610000477 -0500
@@ -576,7 +576,7 @@
    }
 }
 
-if ( ($Detail == 7 && keys %KrbRealm > 1) || ($Detail > 8 && keys %KrbRealm) ){
+if ( ($Detail == 7 && keys %KrbRealm > 1) || ($Detail >= 8 && keys %KrbRealm) ){
    print "\nSucessfull Kerberos Authentication from ",(scalar keys %KrbRealm)," realm:\n";
    foreach my $realm (keys %KrbRealm) {
       if($Detail > 9){

Version-Release number of selected component (if applicable):
logwatch-7.3.6-52.el6.noarch

Comment 7 errata-xmlrpc 2017-03-21 09:32:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0610.html