Bug 894191 - Logwatch doesn't proper ignore "password check failed for user"
Summary: Logwatch doesn't proper ignore "password check failed for user"
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logwatch
Version: 6.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Ondrej Hudlicky
Depends On:
TreeView+ depends on / blocked
Reported: 2013-01-11 00:06 UTC by Robert Scheck
Modified: 2018-12-02 18:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 894272 (view as bug list)
Last Closed: 2013-09-10 13:40:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
[Patch] handle usernames correctly (1.04 KB, patch)
2013-01-14 13:39 UTC, Jan Synacek
no flags Details | Diff

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1247 0 normal SHIPPED_LIVE logwatch bug fix update 2013-09-10 17:38:05 UTC

Description Robert Scheck 2013-01-11 00:06:19 UTC
Description of problem:
/usr/share/logwatch/scripts/services/secure:212 is currently:

  ( $ThisLine =~ /password check failed for user \([a-zA-Z]*\)/) or

Unfortunately this does not match our (system) users, which are "customer_01"
or "example_02" (of course without the "").

Version-Release number of selected component (if applicable):

How reproducible:
Everytime, see above and below.
Actual results:
Logwatch doesn't proper ignore "password check failed for user"

Expected results:
From my point of view, a proper fix for this could be:

  ( $ThisLine =~ /password check failed for user \(\S*\)/) or

Comment 2 Jan Synacek 2013-01-14 13:39:16 UTC
Created attachment 678234 [details]
[Patch] handle usernames correctly

Comment 3 Robert Scheck 2013-01-18 10:08:38 UTC
Patch looks basically fine to me, if manually applied

Comment 11 errata-xmlrpc 2013-09-10 13:40:36 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.


Note You need to log in before you can comment on or make changes to this bug.