Ubuntu
logwatch package

unmatched entry for securetty on focal

Bug #1890751 reported by Bryce Harrington on 2020-08-06

This bug affects 1 person

	Status	Importance	Assigned to
logwatch (Ubuntu)	Fix Released	Medium	Unassigned
Focal	Fix Released	Medium	Unassigned
Groovy	Fix Released	Medium	Unassigned

Bug Description

[Impact]

Messages about /etc/securetty aren't being handled by logwatch and end up in the "Unmatched Entries" section. Support for /etc/securetty was dropped in focal, but some services or other software haven't been updated to reflect this change and so issue the warning.

[Test Case]

$ export CODENAME="focal"
$ lxc launch ubuntu:${CODENAME} test-logwatch
$ lxc exec test-logwatch -- bash

# apt-get update
# apt-get dist-upgrade -y
# apt-get install -y logwatch

# wget https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890751/+attachment/5407063/+files/unmatched-entries-securetty%3Aauth.log
# cat unmatched-entries-securetty:auth.log >> /var/log/auth.log

# logwatch --detail High --service all --range all --output stdout

Without the fix, there will be unmatched entries for /etc/securetty, which may appear in multiple sections within the report; with the fix there will be no such messages.

(Note: For testing it's not really necessary to trigger the original condition that produces the log entry, since for Logwatch the purpose is more about making sure the entry is detected and processed appropriately.)

[Regression Potential]

Since logwatch filters logs for errors pertinent to administrators,
standard things to watch out for are undesired changes in this filtering
behavior, such as flagging or failing to flag issues differently than
before, other than the specific messages being filtered with this
change.

[Original Report]

$ sudo logwatch --detail Low --range today --service all --output stdout

--------------------- pam_unix Begin ------------------------

sudo:
    Sessions Opened:
       root -> root: 4 Time(s)
    Unknown Entries:
       Couldn't open /etc/securetty: No such file or directory: 4 Time(s)

---------------------- pam_unix End -------------------------

See original description

Tags:

Related branches

~bryce/ubuntu/+source/logwatch:logwatch-merge-v7.5.4-1-hirsute

Merged into ubuntu/+source/logwatch:debian/sid at revision 81524f106bc51d386934b66fcbc0511ff624e877

Bryce Harrington (community): Approve on 2020-11-06

Christian Ehrhardt  (community): Needs Fixing on 2020-11-06

Canonical Server: Pending requested 2020-11-05

~bryce/ubuntu/+source/logwatch:fix-unmatched-entries-focal

Merged into ubuntu/+source/logwatch:ubuntu/focal-devel at revision c7185e41e4a9554b1611d0c6a801abf8f78911ed

Christian Ehrhardt  (community): Approve on 2020-09-04

Canonical Server: Pending requested 2020-09-05

Sergio Durigan Junior: Pending requested 2020-09-03

Canonical Server packageset reviewers: Pending requested 2020-09-03

~bryce/ubuntu/+source/logwatch:fix-unmatched-entries-groovy

Merged into ubuntu/+source/logwatch:ubuntu/devel at revision a1388e93369f955a44ef06a0374c678d7b9fc643

Seth Arnold (community): Approve on 2020-08-25

Canonical Server: Pending requested 2020-08-21

Canonical Server Core Reviewers: Pending requested 2020-08-21

Canonical Server packageset reviewers: Pending requested 2020-08-21

Revision history for this message

Bryce Harrington (bryce) wrote on 2020-08-18:

I've reproduced this in lxd on groovy and focal, but not on xenial or bionic.

Changed in logwatch (Ubuntu Groovy):
importance:	Undecided → Medium
status:	New → Triaged
Changed in logwatch (Ubuntu Focal):
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-08-26:

This bug was fixed in the package logwatch - 7.5.4-0ubuntu2

---------------
logwatch (7.5.4-0ubuntu2) groovy; urgency=medium

  [ Bryce Harrington ]
  * d/p/0020-dhcpd-Ignore-lease-age-under-threshold-messages.patch:
    dhcpd: Ignore lease age under threshold messages
    (LP: #1578001)
  * d/p/0019-exim-Handle-self-signed-certs-warnings.patch:
    exim: Handle self-signed certs warnings.
    (LP: #1892269)
  * d/p/0018-audit-Treat-Denial-Errors-same-as-Denied.patch:
    audit: Treat Denial-Errors same as Denied.
    (LP: #1577948)
  * d/p/0017-audit-Apparmor-DENIED-entries-don-t-always-include-p.patch:
    audit: Apparmor DENIED entries don't always include parent=N.
    (LP: #1577948)
  * d/p/0015-pam_unix-Ignore-issues-about-etc-securetty-being-mis.patch:
    pam_unix: Ignore issues about /etc/securetty being missing.
    (LP: #1890751)
  * d/p/0014-zz-sys-Suppress-warnings-if-Sys-CPU-or-Sys-MemInfo-a.patch:
    zz-sys: Suppress warnings if Sys::CPU or Sys::MemInfo are missing.
    These are not installed by default in Ubuntu's logwatch packaging.
    (LP: #1890749)
  * d/p/0013-secure-Ignore-warnings-about-gnome-keyring-daemon-it.patch:
    secure: Ignore warnings about gnome-keyring-daemon items already
    registered.
    (LP: #1890752)
  * d/p/0012-postfix-Handle-backwards-compatible-mode.patch:
    postfix: Handle backwards-compatible mode.
    (LP: #1583705)
  * d/p/0011-postfix-Ignore-Resolved-loghost-to-127.0.0.1.patch:
    postfix: Ignore Resolved loghost to 127.0.0.1.
    (LP: #1583705)
  * d/control: Update upstream's homepage
    (LP: #1891604)

  [ Lucas Kanashiro ]
  * d/p/0021-audit-use-the-term-ALLOWED-instead-of-Grants.patch:
    audit: use the term ALLOWED instead of Grants.

-- Bryce Harrington <email address hidden> Fri, 21 Aug 2020 01:30:10 +0000

Changed in logwatch (Ubuntu Groovy):
status:	Triaged → Fix Released

Revision history for this message

Bryce Harrington (bryce) wrote on 2020-09-02:

Sample log entries for testing the securetty error messages Edit (213 bytes, text/plain)

Revision history for this message

Bryce Harrington (bryce) wrote on 2020-09-02:

See also:
  https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899

"FWIW, the latest login upload to unstable (1:4.7-1) dropped support for /etc/securetty and removed that file on upgrades, due to the numerous complaints it caused... This lead to complaints by pam_unix in the system logs on every login, see #931899."

So the warning is superfluous, and merely serves to cause confusion for other unrelated bugs (e.g. LP #1860826 comments 8-12).

Apparently a workaround is to remove "nullok_secure" from the auth line in /etc/pam.d/common-auth.

Logwatch sounds unsure about carrying this change upstream, but given the above I think it is worth carrying in the Ubuntu delta at least. When LP: #1860826 is resolved for -devel and all supported LTS' the logwatch delta could be dropped, although the messages likely will linger in log files and thus show up in "--range All" for some time.

focal and groovy have login 1:4.8.1-1 so are affected, but bionic has 1:4.5-1 so this is only applicable for SRU to focal.

Revision history for this message

Brian Murray (brian-murray) wrote on 2020-09-15: Please test proposed package

Hello Bryce, or anyone else affected,

Accepted logwatch into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/logwatch/7.5.2-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in logwatch (Ubuntu Focal):
status:	Triaged → Fix Committed
tags:	added: verification-needed verification-needed-focal

Bryce Harrington (bryce) on 2020-09-15

description:

updated

Revision history for this message

Bryce Harrington (bryce) wrote on 2020-09-29:

Verified on focal in LXC that the securetty messages are suppressed.

Bryce Harrington (bryce) on 2020-09-29

tags:

added: verification-done verification-done-focal
removed: verification-needed verification-needed-focal

Revision history for this message

Launchpad Janitor (janitor) wrote on 2020-09-29:

This bug was fixed in the package logwatch - 7.5.2-1ubuntu1.1

---------------
logwatch (7.5.2-1ubuntu1.1) focal; urgency=medium

  [ Bryce Harrington ]
  * d/p/0020-dhcpd-Ignore-lease-age-under-threshold-messages.patch:
    dhcpd: Ignore lease age under threshold messages
    (LP: #1578001)
  * d/p/0019-exim-Handle-self-signed-certs-warnings.patch:
    exim: Handle self-signed certs warnings.
    (LP: #1892269)
  * d/p/0018-audit-Treat-Denial-Errors-same-as-Denied.patch:
    audit: Treat Denial-Errors same as Denied.
    (LP: #1577948)
  * d/p/0017-audit-Apparmor-DENIED-entries-don-t-always-include-p.patch:
    audit: Apparmor DENIED entries don't always include parent=N.
    (LP: #1577948)
  * d/p/0015-pam_unix-Ignore-issues-about-etc-securetty-being-mis.patch:
    pam_unix: Ignore issues about /etc/securetty being missing.
    (LP: #1890751)
  * d/p/0014-zz-sys-Suppress-warnings-if-Sys-CPU-or-Sys-MemInfo-a.patch:
    zz-sys: Suppress warnings if Sys::CPU or Sys::MemInfo are missing.
    These are not installed by default in Ubuntu's logwatch packaging.
    (LP: #1890749)
  * d/p/0013-secure-Ignore-warnings-about-gnome-keyring-daemon-it.patch:
    secure: Ignore warnings about gnome-keyring-daemon items already
    registered.
    (LP: #1890752)
  * d/p/0012-postfix-Handle-backwards-compatible-mode.patch:
    postfix: Handle backwards-compatible mode.
    (LP: #1583705)
  * d/p/0011-postfix-Ignore-Resolved-loghost-to-127.0.0.1.patch:
    postfix: Ignore Resolved loghost to 127.0.0.1.
    (LP: #1583705)
  * d/p/0010-00-debspecific-disable-su-reporting-in-secure.diff.patch:
    Use $PATH to determine location of zpool and zfs.
    (LP: #1880211)

  [ Lucas Kanashiro ]
  * d/p/0021-audit-use-the-term-ALLOWED-instead-of-Grants.patch:
    audit: use the term ALLOWED instead of Grants.
    (LP: #1577948)

-- Bryce Harrington <email address hidden> Thu, 03 Sep 2020 04:22:00 +0000

Changed in logwatch (Ubuntu Focal):
status:	Fix Committed → Fix Released

Revision history for this message

Brian Murray (brian-murray) wrote on 2020-09-29: Update Released

The verification of the Stable Release Update for logwatch has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.