Ubuntu
logwatch package

~bryce/ubuntu/+source/logwatch:sru-lp1880211-groovy

  1. Git
  2. lp:~bryce/ubuntu/+source/logwatch
  3. sru-lp1880211-groovy
Last commit made on 2021-04-14
Get this branch:
git clone -b sru-lp1880211-groovy https://git.launchpad.net/~bryce/ubuntu/+source/logwatch
Only Bryce Harrington can upload to this branch. If you are Bryce Harrington please log in for upload directions.

Branch merges

Branch information

Name:
sru-lp1880211-groovy
Repository:
lp:~bryce/ubuntu/+source/logwatch

Recent commits

ffedd59... by Bryce Harrington

changelog

d0f80d9... by Bryce Harrington

  * d/p/0010-zz-zfs-detect-zfs-location.patch: Use explicit paths for
    finding zfs and zpool executables.
    (LP: #1880211)

50e66ce... by Bryce Harrington

changelog

81e0fe4... by Bryce Harrington

  * d/p/0021-audit-use-the-term-ALLOWED-instead-of-Grants.patch:
    Fix typo in variable '$allawed'; refresh patch.

37f629b... by Bryce Harrington

  * d/p/0018-audit-Treat-Denial-Errors-same-as-Denied.patch:
    Update DEP3 to link to where this patch was forwarded upstream.

e628747... by Bryce Harrington

  * d/p/0014-zz-sys-Suppress-warnings-if-Sys-CPU-or-Sys-MemInfo-a.patch:
    Update DEP3 to indicate this patch does not need forwarded upstream
    since it corrects a distro packaging issue.

b29f728... by Lucas Kanashiro

Update changelog

cd48c83... by Lucas Kanashiro

d/p/0021-audit-use-the-term-ALLOWED-instead-of-Grants.patch:
audit: use the term ALLOWED instead of Grants

This was not submitted upstream yet but it was a suggestion made by the
Ubuntu Security team.

2c00a18... by Lucas Kanashiro

Update d/p/0018-audit-Treat-Denial-Errors-same-as-Denied.patch

Squashed the previous patch with the new version Bryce is proposing to upstream:

audit: Treat Denial Errors same as Denied

Ubuntu Security says, "I think this would be more useful as DENIED, as
that's how we discuss these line events elsewhere."

7ffa410... by Lucas Kanashiro

Update d/p/0017-audit-Apparmor-DENIED-entries-don-t-always-include-p.patch

Squashed the previous patch with the new version Bryce is proposing to upstream:

audit: Don't handle "unconfined" profile changes distinct from ordinary loads

Per the Ubuntu Security team, these messages don't indicate *dropping*
confinement, but that the AppArmor parser was running unconfined when it
changed the policy. This occurs very commonly during reboot, snap
refresh, libvirt vm launch, etc. They don't need special tracking.