Small updates for changed outputs
Small updates for changed outputs
Match some updated output
Fix output of blank sendmail section when not running
Update termination message
Murray, I'll take a shot at this, as a long time user and occassional contributor. First off, logwatch only reports what is in the logs, it does not interpret if they are good or bad. The fact you are getting these logged really goes back to your firewall package, and you may want to see if you can supress the logging from there. Note, I say supress the logging, not disable the actual rule. Now if that is not possible for whatever reason, you should look at the documenataion on how to customise logwatch,...
Suppress newline when no other output generated
Suppress newline when no other output generated
Suppress excess new line when no output generated
Ignore virtual filesystem nsfs
Ignore virtual filesystem nsfs
Exclude virtual FS nsfs
Fix dnf5 giving time in UTC
Fix dnf5 giving time in UTC
Remove tabs and clean up formatting
Handle dnf5 returning times as UTC
There is a timezone bug here to be fixed, dnf5 currently reports all times as GMT, not local, but we assume it is local, as there is no indication of timezone. I'll get this fixed in the module, but the DNF team plan to fix it sometime, no timeline yet, and no idea how they will show it.
John, Obviously a separate issue, but I will see what I can find. On a more positive note, the fix for SELinux was pushed today, so it should now work automatically. Frank
This is better to take up in RedHat bugzilla, which already does have one raised, with relevant details. But to be more specific, this is really a SELinux issue, and there is a ticket in to fix it. Unfortunately it has not yet been released. There are two short term solutions, either semanage permissive -a logwatch_t or a more specific SELinux module allowing the required transition (which will be in the updated SELinux policy update).
Add new script to process dnf5 reports
Add new script to process dnf5 reports
Add new script to process dnf5 reports
Sync state
Sync state
I'll look at rolling this up into a more standard logwatch script, as long as no one is worried about directly using the output from dnf rather than reading any log files. From some previous research I did, the only place it is logged is in the audit files as type=SOFTWARE_UPDATE but I don't believe it has as much detail as the output from dnf.
Change in format for some messages in Fedora 39
Fix uninitialized value in PrettyTimes
Ignore qname minimsation due to ncache nxdomain
Fix for mdadm in Fedora 38 and for named DNS format error report
Fix for mdadm in Fedora 38 and for named DNS format error report
Sync
Sync
Better handling of spaces in DNSSEC errors
Better handling of spaces in DNSSEC errors
Add MissingCookie to named
Add MissingCookie to named
Yes, it is a deliberate change. See commit 8aade3ed559c8a60aa94715d202373ddffbd5a12 Author: Orion Poplawski <orion@nwra.com> Date: Thu Jun 2 11:58:08 2022 -0600 [fail2ban] Only emit banned summary for Detail > 0 @opoplawski may be able to give a reason why this was done. An easy fix is to run with Detail=1 in the fail2ban.conf file.
Ignore adb growth messages for named
Ignore adb growth messages for named
Minor additional updates
Minor additional updates
Fix regression for older systemd in Fedora 36
Fix regression for older systemd in Fedora 36
Match new messages found in Fedora 37
Match new messages found in Fedora 37
Match new messages found in Fedora 37
Match new messages found in Fedora 37
Update sshd for multiline key exchange errors
Update sshd for multiline key exchange errors
Unmatched entries related to MaxStartups throttling in OpenSSH
Joe, I've taken your original code, expanded it with some more information at higher detail levels and now merged it into the tree. You can either pull down the latest version in the git repo, or wait until the next version of Logwatch is released, which should be in a month or so. Thanks Frank
Process MaxStartups messages for SSHD
Process MaxStartups messages for SSHD
Will do, although I may expand it a little with some more stats for higher levels of detail.
Joe, Having a quick look at it, I don't see anything wrong with it. I'll give it a quick test. I notice that you are also cleaning up some other formatting, which is not a problem. If you want to create a PR for it, feel free, or if you want me to just roll it into the current code, I can do that. Regards Frank
Joe, Do you have any code to match them? I've also been thinking of reporting on them, but was stuck with what do we want to not for them? Would it just be a count of MaxStartups by IP address, or something more complicated? Frank
Update for some message format changes
Handle some minor message format changes
Ignore startup messages and handle other minor changes
Ignore message on informational messages
Ignore message on logging shutdown
Pull latest.
Pull latest.
A quick question, have you logged this issue with RedHat? The version of Logwatch they are running is old, and they are reluctant to upgrade it, because "it currently works fine".
Match minor change in systemd
Minor update to systemd Session details
Minor update to systemd Session details
Fixes for LVM Reports
Updates for Fedora 33
Fixes for LVM Reports
Updates for Fedora 33
Update for release 1.5.1
Update man pages on website to latest
Scott, I'll have a look at this over the next few days, as it used to work, and I believe should still be working.
Handle count mismatch for updates
Add report on IPv6 DNS updates
Minor updates from Fedora 32
Yes, you are correct. Good catch. I'll update it.
Handle count mismatch for updates