You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(7) |
Apr
(6) |
May
(17) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(7) |
Oct
(5) |
Nov
(14) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(22) |
Feb
(52) |
Mar
(11) |
Apr
(5) |
May
(8) |
Jun
(18) |
Jul
(6) |
Aug
(6) |
Sep
|
Oct
(6) |
Nov
(6) |
Dec
(11) |
| 2012 |
Jan
(5) |
Feb
(4) |
Mar
(2) |
Apr
(37) |
May
(10) |
Jun
(2) |
Jul
(4) |
Aug
(1) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(10) |
| 2013 |
Jan
(15) |
Feb
(7) |
Mar
(3) |
Apr
|
May
(10) |
Jun
(35) |
Jul
(10) |
Aug
(25) |
Sep
(1) |
Oct
(3) |
Nov
(9) |
Dec
(3) |
| 2014 |
Jan
(15) |
Feb
(11) |
Mar
|
Apr
|
May
(28) |
Jun
(9) |
Jul
(6) |
Aug
(10) |
Sep
(76) |
Oct
(8) |
Nov
(3) |
Dec
(19) |
| 2015 |
Jan
(10) |
Feb
(4) |
Mar
(5) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(3) |
Dec
(1) |
| 2016 |
Jan
(12) |
Feb
(34) |
Mar
(10) |
Apr
(7) |
May
(5) |
Jun
(2) |
Jul
(3) |
Aug
(4) |
Sep
(11) |
Oct
(1) |
Nov
(13) |
Dec
(18) |
| 2017 |
Jan
(28) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(5) |
Dec
(3) |
| 2019 |
Jan
(7) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(3) |
Oct
(3) |
Nov
(2) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(7) |
Nov
(4) |
Dec
|
| 2021 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(2) |
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2026 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Daniel L. <le...@gm...> - 2021-10-05 02:50:01
|
Logwatch Developers,
OS: Debian GNU/Linux 11 (bullseye)
Logwatch 7.5.5-1
Exim 4.94.2-7
Logwatch is reporting this:
--------------------- EXIM Begin ------------------------
Use of uninitialized value $SelfSigned in concatenation (.) or string at
/usr/share/logwatch/scripts/services/exim line 334, <STDIN> line 383.
--- Self-Signed Certificate in use ( Time(s))
---------------------- EXIM End -------------------------
Below is a one-line patch which fixes this.
Thank you!
Daniel Lewart
Urbana, Illinois
--- scripts/services/exim.orig 2020-09-07 15:43:26.000000000 -0500
+++ scripts/services/exim 2021-10-05 00:00:00.000000000 -0500
@@ -329,7 +329,7 @@
}
}
-if (@SelfSignedH) {
+if ($SelfSigned) {
print "\n--- Self-Signed Certificate in use ($SelfSigned Time(s))\n";
if ($Detail >= $LvlMsgs) {
|
|
From: Threet, R. A <rob...@us...> - 2021-05-20 20:49:13
|
Ah, a matching .conf file was needed. Got it working! This is great!
Robert Threet
Systems Manager
Information Technology
(812) 465-1082
Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
________________________________
From: Threet, Robert A <rob...@us...>
Sent: Wednesday, May 19, 2021 2:07 PM
To: Mike Tremaine <mg...@st...>
Cc: log...@li... <log...@li...>
Subject: Re: [Logwatch-devel] Easy way to add /etc/motd to Logwatch report?
*** This message was sent from a non-USI address. Please exercise caution when responding, clicking on links or opening attachments. ***
Ok, first time to attempt this. What I did:
Copied zz-runtime to zz-motd
s/uptime/motd/g
s/Uptime/MOTD/g
Removed line:
my $show_motd = $ENV{'show_motd'} || 0;
Modified line:
if (($ENV{'PRINTING'} eq "y" ) && $show_motd && $motd) {
to
if (($ENV{'PRINTING'} eq "y" ) && $motd) {
Result (which doesn't work despite config set to Services = ALL):
bash-5.1# pwd
/usr/share/logwatch/scripts/services
bash-5.1# cat zz-motd
########################################################
# Please file all bug reports, patches, and feature
# requests under:
# https://sourceforge.net/p/logwatch/_list/tickets
# Help requests and discusion can be filed under:
# https://sourceforge.net/p/logwatch/discussion/
########################################################
#######################################################
## Copyright (c) 2008 Kirk Bauer
## Covered under the included MIT/X-Consortium License:
## http://www.opensource.org/licenses/mit-license.php
## All modifications and contributions by other persons to
## this script are assumed to have been donated to the
## Logwatch project and thus assume the above copyright
## and licensing terms. If you want to make contributions
## under your own copyright or a different license this
## must be explicitly stated in the contribution an the
## Logwatch project reserves the right to not accept such
## contributions. If you have made significant
## contributions to this script and want to claim
## copyright please contact log...@li....
#########################################################
my $motd=`cat /etc/motd`;
if (($ENV{'PRINTING'} eq "y" ) && $motd) {
print "\nMOTD: $motd\n";
}
# vi: shiftwidth=3 tabstop=3 syntax=perl et
# Local Variables:
# mode: perl
# perl-indent-level: 3
# indent-tabs-mode: nil
# End:
Robert Threet
Systems Manager
Information Technology
(812) 465-1082
Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
________________________________
From: Mike Tremaine <mg...@st...>
Sent: Tuesday, May 18, 2021 8:07 PM
To: Threet, Robert A <rob...@us...>
Cc: log...@li... <log...@li...>
Subject: Re: [Logwatch-devel] Easy way to add /etc/motd to Logwatch report?
*** This message was sent from a non-USI address. Please exercise caution when responding, clicking on links or opening attachments. ***
Take a look at one of the simpler scripts like zz-runtime [ by default in /usr/share/logwatch/scripts/services ]
You could roll your own service by copying that and then added the configuration or you could just as easily just hack that one to add your output.
-Mike
On May 18, 2021, at 1:19 PM, Threet, Robert A <rob...@us...<mailto:rob...@us...>> wrote:
I have some information going into /etc/motd that refreshes 3x a week and is unique to the server. I would like that added to my logwatch report.
Seems like it'd be easy?
Robert Threet
Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
_______________________________________________
Logwatch-devel mailing list
Log...@li...<mailto:Log...@li...>
https://lists.sourceforge.net/lists/listinfo/logwatch-devel<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Flogwatch-devel&data=04%7C01%7Crobert.threet%40usi.edu%7C7368f174b5b74227d2fc08d91afb7a95%7Cae1d882c786b492c90953d81d0a2f615%7C0%7C1%7C637570489667278239%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ywraetL5y9xOfHmU0fA04fLP0vsVoOUZQsC%2BVGITZGo%3D&reserved=0>
|
|
From: Threet, R. A <rob...@us...> - 2021-05-19 19:22:40
|
Ok, first time to attempt this. What I did:
Copied zz-runtime to zz-motd
s/uptime/motd/g
s/Uptime/MOTD/g
Removed line:
my $show_motd = $ENV{'show_motd'} || 0;
Modified line:
if (($ENV{'PRINTING'} eq "y" ) && $show_motd && $motd) {
to
if (($ENV{'PRINTING'} eq "y" ) && $motd) {
Result (which doesn't work despite config set to Services = ALL):
bash-5.1# pwd
/usr/share/logwatch/scripts/services
bash-5.1# cat zz-motd
########################################################
# Please file all bug reports, patches, and feature
# requests under:
# https://sourceforge.net/p/logwatch/_list/tickets
# Help requests and discusion can be filed under:
# https://sourceforge.net/p/logwatch/discussion/
########################################################
#######################################################
## Copyright (c) 2008 Kirk Bauer
## Covered under the included MIT/X-Consortium License:
## http://www.opensource.org/licenses/mit-license.php
## All modifications and contributions by other persons to
## this script are assumed to have been donated to the
## Logwatch project and thus assume the above copyright
## and licensing terms. If you want to make contributions
## under your own copyright or a different license this
## must be explicitly stated in the contribution an the
## Logwatch project reserves the right to not accept such
## contributions. If you have made significant
## contributions to this script and want to claim
## copyright please contact log...@li....
#########################################################
my $motd=`cat /etc/motd`;
if (($ENV{'PRINTING'} eq "y" ) && $motd) {
print "\nMOTD: $motd\n";
}
# vi: shiftwidth=3 tabstop=3 syntax=perl et
# Local Variables:
# mode: perl
# perl-indent-level: 3
# indent-tabs-mode: nil
# End:
Robert Threet
Systems Manager
Information Technology
(812) 465-1082
Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
________________________________
From: Mike Tremaine <mg...@st...>
Sent: Tuesday, May 18, 2021 8:07 PM
To: Threet, Robert A <rob...@us...>
Cc: log...@li... <log...@li...>
Subject: Re: [Logwatch-devel] Easy way to add /etc/motd to Logwatch report?
*** This message was sent from a non-USI address. Please exercise caution when responding, clicking on links or opening attachments. ***
Take a look at one of the simpler scripts like zz-runtime [ by default in /usr/share/logwatch/scripts/services ]
You could roll your own service by copying that and then added the configuration or you could just as easily just hack that one to add your output.
-Mike
On May 18, 2021, at 1:19 PM, Threet, Robert A <rob...@us...<mailto:rob...@us...>> wrote:
I have some information going into /etc/motd that refreshes 3x a week and is unique to the server. I would like that added to my logwatch report.
Seems like it'd be easy?
Robert Threet
Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.
_______________________________________________
Logwatch-devel mailing list
Log...@li...<mailto:Log...@li...>
https://lists.sourceforge.net/lists/listinfo/logwatch-devel<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Flogwatch-devel&data=04%7C01%7Crobert.threet%40usi.edu%7C5817424131444e2d6bd508d91a627f42%7Cae1d882c786b492c90953d81d0a2f615%7C0%7C0%7C637569832613431718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ao8xRErtkGXc95oiPU2pjsTtYyk3%2B5wOgbsZMokHK5g%3D&reserved=0>
|
|
From: Mike T. <mg...@st...> - 2021-05-19 01:20:48
|
Take a look at one of the simpler scripts like zz-runtime [ by default in /usr/share/logwatch/scripts/services ] You could roll your own service by copying that and then added the configuration or you could just as easily just hack that one to add your output. -Mike > On May 18, 2021, at 1:19 PM, Threet, Robert A <rob...@us...> wrote: > > I have some information going into /etc/motd that refreshes 3x a week and is unique to the server. I would like that added to my logwatch report. > > Seems like it'd be easy? > > > Robert Threet > Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. > _______________________________________________ > Logwatch-devel mailing list > Log...@li... <mailto:Log...@li...> > https://lists.sourceforge.net/lists/listinfo/logwatch-devel <https://lists.sourceforge.net/lists/listinfo/logwatch-devel> |
|
From: Threet, R. A <rob...@us...> - 2021-05-19 00:56:38
|
I have some information going into /etc/motd that refreshes 3x a week and is unique to the server. I would like that added to my logwatch report. Seems like it'd be easy? Robert Threet Confidentiality Statement: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. |
|
From: Jason P. <jp...@pd...> - 2021-01-23 03:57:58
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 renamed cygwin rpm, linux rpm signatures added e005ac67a9e78060310cdfb352ef16e8 *logwatch-7.5.5-1.noarch.rpm 10cc980a21ebe9e6d536eab60ff18e4b445e8f99 *logwatch-7.5.5-1.noarch.rpm 1d08dc467761f0398e3cec7739cd903edf4154b26bb2204371ba8e9a8c22b889 *logwatch-7.5.5-1.noarch.rpm cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5-1.noarch.cygwin.rpm ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.cygwin.rpm 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.cygwin.rpm -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJgC56jAAoJEMHgKYWVivCRnEIQAIdW2Bf4JOf3grcr0X7oD444 f92P71/celDKWhaz46P7T8WgmQjGcui0X+9NQNecpx5pUbL5fNkd2bL9jr3yXSuc 5RK7RUa5rMo1iuimdrBiGYWSVGcRKMn61FcYR71/bokw5hsStHB3OFlF+l/IeI8P Ja6gjzYruN4CLZTpxvM4uXAWoY6cjQx4U1BYTgLEF+/NgNJVbqo66J/Ru/dwQJoH TTIbwU6yvFbNtTg8cqgrcLSiknbqLkPRrUgtVio5CoTb/9GGKNK543DNiRA4NOFU /HLTNYSPwyXUP6nGb2YkQKBhrn/dzbSu3q4mCYJPezg/PZRmjKNClIwDQOcz+PbF EazKasLFERRoMiqHz1NEEa66mgpOB9Lr+2+nDQBBHOe6T0T0mbhjR8YGMkPBhdaO 1r/d9O6LloxTQTvszk13PfKnkgHJQ9tx8aewDQ513e/yOB+7gOoJ43QqtRsP7I2W 4d+pfwn3AzoBbzRGfv4ajg2hFeo34CSGjvPX5g7q9bb8CPlVz0bd1UdHMkAYrNot ORySN+mtsRLcWbRqJuhwr17q4wDPU75cD09MMVmg5Gaim/gFdVLYyVtQ2spOusFU J+hYJI/Z0C8cPWlAY6Yi3IfvvF89Db94jtCeW/OESxuayiY+O/nRUfXU/hnGNWH3 BQCstOZzcq/UqNwTseXj =9Uoo -----END PGP SIGNATURE----- > -----Original Message----- > From: Jason Pyeron [mailto:jp...@pd...] > Sent: Friday, January 22, 2021 8:08 PM > To: log...@li... > Subject: Re: [Logwatch-devel] release 7.5.5 > > Sorry, signed that last message with a test key - apologies. > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > SHA 256, 1, and MD5 sums for release 7.5.5 (git commit > a8bdb8ba8915339a5b2383b445cd8280aa88b637) > > cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5- > 1.noarch.rpm > fad38d6880db7f22196d160b0b83e52a124f7ced074a230316e90e905b12ce99 *logwatch-7.5.5-1.src.rpm > 138f181dea49470e1ef2d39af11b851aef0156500601312ce4de25d3a199b1c1 *logwatch-7.5.5.tar.gz > ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.rpm > b201a97d0fb467190456c8998dc8c9d61c65e971 *logwatch-7.5.5-1.src.rpm > f4e8ed4f846758be78b3d55791a867d70a197226 *logwatch-7.5.5.tar.gz > 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.rpm > 44654aec8e84c5c6ef2754bc0acaf6fa *logwatch-7.5.5-1.src.rpm > b658e4db27d905151396ecadcbcb24b1 *logwatch-7.5.5.tar.gz > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBAgAGBQJgC3alAAoJEMHgKYWVivCRgRAQAKXWpj0J+FcOAFLsVeM7WVa7 > nbHGuAUALc8ogQ/x7HDcVgGTneAljlrrMN0Nmmv5CToQcd5ltAnqyWzyVpYTlbJQ > pJdAflFkh4cjeQs2QjYGJT15vjQMjsWpD4JW95g3ZwkOk2Odm5zIn9GN1+fWXr4Y > sqpgtslMGAePFirqRtw+mQQf0UdGAiWKiyyuEUPKjtbkx+DEEIIVAm5ijIAp/z5G > XkrUN0QVndheziKiqjwjdUkc6pbC/wGe5gdmveYRgu+izpnqyVQ5Sco91VFxpgAg > QR+f+r3bhWNEymLWOMX1CQfNdweQzEZICDOIZlg7DfFDg/ZorBxHIqInPBGmTED2 > aQbQkbWJh51iQH+3E3lNH4xuCO3bOtqoF311je9/lKunDNfKbgfdXvt6RD0jCYKe > P1sf8RfZ1y6347sivlHyQeD7hWKA4YFlWJpcXoWDypV05O3elIJOkmF/yVNJt6iM > xBx8cF1yf18lAzVqUyM4piEQ57GnKPRvKUrBk+XjOIG9fH+SCfeeq7eWz5G9ul85 > tXDho5ICsHe7+92Wh+ywFubhuW4Ia2KU6XYZojmtsKQQKW2yxCohUgcJf3ElYzOu > pq3VzrBb9VU6iNiilDSZIpTW3kXu5OUn7V3RW9DuaimRmL3SrAUsJNo3ujKDfi2o > ikYTd44sudivh3B9MyfD > =2YsP > -----END PGP SIGNATURE----- > > > -----Original Message----- > > From: Jason Pyeron [mailto:jp...@pd...] > > Sent: Friday, January 22, 2021 4:58 PM > > To: log...@li... > > Subject: [Logwatch-devel] release 7.5.5 > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > SHA 256, 1, and MD5 sums for release 7.5.5 (git commit > > a8bdb8ba8915339a5b2383b445cd8280aa88b637) > > > > cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5- > > 1.noarch.rpm > > fad38d6880db7f22196d160b0b83e52a124f7ced074a230316e90e905b12ce99 *logwatch-7.5.5- > 1.src.rpm > > 138f181dea49470e1ef2d39af11b851aef0156500601312ce4de25d3a199b1c1 *logwatch-7.5.5.tar.gz > > ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.rpm > > b201a97d0fb467190456c8998dc8c9d61c65e971 *logwatch-7.5.5-1.src.rpm > > f4e8ed4f846758be78b3d55791a867d70a197226 *logwatch-7.5.5.tar.gz > > 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.rpm > > 44654aec8e84c5c6ef2754bc0acaf6fa *logwatch-7.5.5-1.src.rpm > > b658e4db27d905151396ecadcbcb24b1 *logwatch-7.5.5.tar.gz > > -----BEGIN PGP SIGNATURE----- > > > > iQIcBAEBAgAGBQJgC0pFAAoJEBA+OntaaKB7OhAP/0DivXXmQj7QELCYerg9/h0i > > YKlx9e77ZbOhQyqa3pgUFFXYBB+FTZW12MxWcAI1hJ/eky03sUBif7cFxajb4GjZ > > 6y80p5eJQFb8o5mo+dCHX1TPjO63GNLHdzbmx3jcbG6TU6BWlQlY9EO+GzxBGNwt > > I2sjJhJFy6EYz2JbseffQvNGS94u81dLxitJineRw2AYzZ3q5OMPWUwkzHP+9mmz > > Ng42xc3LzuIyZCJfmsoyvMEG9agoXNYqGoZ1kctuOSO1yBc+LGkmVEeg3T9zbzRu > > vtXBWT6RrfQWGJUdz8393vtR4XiqneIFDoNAp3Gc68Iy9kbLCk9WrItHk7ljI3GN > > RWSjpr1/udlaFSgwlVfl8am+Lno/JGmpEUOqAdp0e7BLqMqJ11RWA9RtVRWzvHbM > > DLE2TQKGxF8CDoCnmhhOjqLZeXICn7dTPCFtDGCC/jEXvUACMkGNMx/Okl7SL7uo > > qxFrth0MeOIIIJbrDGX2nO8wJFE6Pl3PE+9jCqdCO9n9IFbIsx9ipeVb131esth6 > > qizPMUmueslxy2lc0vzzxg2YX/gOAbivmArfW5Lb6rBStR2wotPMzxAG8mRBHGfM > > iFRwfe0g0J//YK3CeUoVzJCtoZ+PlRPI++JNYPz6BpGXwlT1EJ4Gh/5z9dh8YjWV > > OhgHVAo3hcd/EiR5QtQz > > =1DuD > > -----END PGP SIGNATURE----- > > > > > > > -----Original Message----- > > > From: Jason Pyeron <jp...@pd...> > > > Sent: Friday, January 22, 2021 2:47 PM > > > To: 'log...@li...' <log...@li...> > > > Subject: My new GPG key 0xC1E02985958AF091 / 0x958AF091 > > > > > > pub 4096R/958AF091 2021-01-22 [expires: 2024-01-22] > > > uid Jason Pyeron <jp...@pd...> > > > > > > pub 4096R/C1E02985958AF091 2021-01-22 [expires: 2024-01-22] > > > uid Jason Pyeron <jp...@pd...> > > > > > > $ gpg --export -a 958AF091 > > > -----BEGIN PGP PUBLIC KEY BLOCK----- > > > > > > mQINBGALKesBEADw+FbnCEDqG1mvddC0KaDzxOJIo+cCa31nY4kDUyaaBVQzNNMT > > > A/U1re7pJmxtT/k+BxAXJGw1VW+49Prxb4yGM0e484rsSkOAGTfhlhKATE8csS25 > > > tRppeSqvTGbWG64DJWa1iKde6xOoFWS8osl382ErCIZjsery7SYKCLSTq9mmvOHM > > > yjMhii1oncQo7zQP/KlDlla7B83KHCR2LH7jhNFNvr1UN5GYYNV4ITQtpxUpiiZ0 > > > mjC96FBbX6lRsMkJDOx1G7e42ik26rUYGfpQUai68gnWSoPE/vZz/i0taFqClZ2c > > > LYQ4sDoU06akVmhhvVUczd5ksPMUylAqjBcaIfU2r0CmsGPBRYMi76WCD4F8Ejjf > > > tSjD/NTJ97oIJzg4nPoYPDaB4+9GfGmFUmS0+SzJeXnE5tAPIUfL90XrJggeS3re > > > 9vmLZSG+fp5iZoW4MnyyLFvvoBy1RBsG/tZiQtIfz6/FT7zniymuPb/7VNuDRRMj > > > zhSMQdHbNifaZjGwHXIlcNen6g5TjfHvUVcawr9dSJK4TpVxjPc1kmY6/8Xssx97 > > > ycm1yxSYb2QPrcQxkCMC/fmHx7eyKeY8tow3TGevfDOHaSEkCGZuQ2V4961DEl0x > > > SC9hQ9bSe2aju2U/dzAApaOnlSKoyHnBFGoZGqGwJGrignXl9AcVK0n0IQARAQAB > > > tB9KYXNvbiBQeWVyb24gPGpweWVyb25AcGRpbmMudXM+iQI+BBMBAgAoBQJgCynr > > > AhsDBQkFo5qABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDB4CmFlYrwkVAK > > > EADhQWU6CalYil5TBl8B1CQXKcD56d9msqm2iptV9oC2ap40VCjG4axMYwXhYJQw > > > FP8owN02m1fxI7BBKOOnhfklDdxQe87cQzajV0jTCI13/7AYf5/RMFWpetNFqU/n > > > HhNxjCo9tIW9MUVM/1nNTRFwGyl/QXTqTfwRkIbRznMPCR2AhA84qjPOkOGgzFkE > > > Q+abjLac0cY12JRblJTIqttOenHwXpkcjTbmP0Rk0PDdsXP6K9UgniVr/DhdFrh0 > > > xnEVfWYRh4nP7qSKosAPJFkDQZzyUcTsW5kZ044bVMYhzmrhokzJ4E+dNzkdUMp7 > > > 2ggdzlmr5s6SttmkrHYBWhsj4gWC3CngunR1H3uUWG6EFpnnLnqhLVCnZ4ONamnC > > > x/Ztv+D7FQq+/xgM+qepRusfCjyunmPjn0PUlyApfD5pXBhupQdvA/N/4MRLgxej > > > v5eTKPSYKQ74y7w0+Mt2wchON5PMX2IK/ydw4SSgRlomblfS3gmIUA9DM5uC++8p > > > NzzqoJzY9+AqnU/kKAVlsoLWs5HZY8g5x0diFtKX1leItA4frlbDIY7HYO/P2GYo > > > e7jnnV3HPbE8/bahOInA+qYUj278pAJIyLig9lHanVQO/3Wm5EbFJGSTaK/u0KCj > > > tpUhs+BRnvVuELZta023HBKQFJgqNRYrGUAUdLATcmpC2LkCDQRgCynrARAAq5wr > > > 2grss7bEPQ6qN0jpec9HBQDznt/6cqps1uhELsR30rI0exlK3ps7SjS1eXotw9w1 > > > FL7Jj6PtVfaXkR5pxL4aL4NIfzHHsguQmQECrnjon0AOMRb2PFqLTAR2seQpTy5i > > > xHOIbxEzurEygphfajfa04CwNtaMAPfoAAWMO3GlhcKkzvjBpUllKvf7GFNKC1i1 > > > +XuHjEdetKNtlQbTkLUNmTvoCj6wYOCShHlyfi6X5/8l7YUFRLdtz18rIKSyG0j/ > > > +CtoZ+Wn+5igObTa6AwLn39eRg3tWAFIvf4/0jgu1j3d5vTwgikFFNQHU7+zbrlP > > > ilSKI6Ne5JBBWDjXR5K8a/7bOHQRT9lO431sWwVN/+m91ZPr56yYv141rGIj67eI > > > +9ISBgM6PhPQx8SsJ00FlllkVDSAHmKXNFDUqSbCpu/MY6RL8/3+5nURbiYK/wYM > > > GwAdg39/P2nrsAWj5x+itaLlp70mjstGXhY80+5M5omwDA/lCxmKiP+Td8lHw/OO > > > 6jmJUPLrIPraBfgjlVrw/ulXGX4UlQvgjMD7WsKcI8ZEmCweIX0BNyS2dnqIGKaR > > > L2JnTmBQtD7j32JvSLTOuz9qr/2xjW6IWlFqeu4pWTY22phDmSPw1Ar+0OQa46GH > > > byxdvtivx5GCLowNXFfMEhEfAinIUdAhW3xFZE0AEQEAAYkCJQQYAQIADwUCYAsp > > > 6wIbDAUJBaOagAAKCRDB4CmFlYrwkbZjD/9L2hOORxzXv6xgnZgMsha2hQWCuggY > > > jdgRCb+qq09PyWzaz/CtYAQh3ooLSAXGYI9NGuNVlEdJ1FWiWNOOw5yOu7aO055w > > > KczBG67N+d1VKB1b9OKv+6btYYi5tptuPuCMmfhggSt/VbsVUTClviKfysxnSfwL > > > NU3lA/fr5E4zZjaWKc9evmXLd7/gbIqlGu/LwgT8I8QWZu9+nl2MG42SELIW5K17 > > > n/BqnBf0VdtAPi1EeenCs+0/g/tnOSdM/n1DvS9dOWRvpcUaA2LQDv49lg4U/K+N > > > 7yRGiVNt5GE8qMAu8rNvAptPB6LUGa0jfpcW/Vdf4F2e+KblwLhluZPu95xXk/Y9 > > > nGGBCj8mq7Ed5WmU7lC6kfZNsyJuk0xvCZzeuvIc2rQTefrfadzAMoV87U9U5QF2 > > > FAJc2OVh1L5ds9HZoear6ykdPz++s/zVQy/sjJSjdQB2AHl4+cHdp30S4FM9jPW9 > > > aUxXcJw6ZlHCpTnWzBfamDAsnqSlSORucP3rs1h9iGrGplaMyasP/ARIA2+isXaO > > > tuQyi1Q8AxhXfRsA12CqHVhIuSpPWmv07kCHGNO1EHplZOEBgLGfrDliz3clfrxH > > > DqS36k8r99pvCyX8bepEI06D/q1HqCRPCx9lm/eVNh2iDAPB0D9l1XJyNTZ2o6wL > > > 0j5dSmw2RjRuHA== > > > =Tfro > > > -----END PGP PUBLIC KEY BLOCK----- > > > > > > This replaces an expired in 2017-01-18 key: 0x8D6B5984DA0848AD > > > > > > -- > > > Jason Pyeron | Architect > > > PD Inc | > > > 10 w 24th St | > > > Baltimore, MD | > > > > > > .mil: jas...@ma... > > > .com: jp...@pd... > > > tel : 202-741-9397 > > > > > > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel |
|
From: Jason P. <jp...@pd...> - 2021-01-23 01:08:20
|
Sorry, signed that last message with a test key - apologies. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SHA 256, 1, and MD5 sums for release 7.5.5 (git commit a8bdb8ba8915339a5b2383b445cd8280aa88b637) cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5-1.noarch.rpm fad38d6880db7f22196d160b0b83e52a124f7ced074a230316e90e905b12ce99 *logwatch-7.5.5-1.src.rpm 138f181dea49470e1ef2d39af11b851aef0156500601312ce4de25d3a199b1c1 *logwatch-7.5.5.tar.gz ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.rpm b201a97d0fb467190456c8998dc8c9d61c65e971 *logwatch-7.5.5-1.src.rpm f4e8ed4f846758be78b3d55791a867d70a197226 *logwatch-7.5.5.tar.gz 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.rpm 44654aec8e84c5c6ef2754bc0acaf6fa *logwatch-7.5.5-1.src.rpm b658e4db27d905151396ecadcbcb24b1 *logwatch-7.5.5.tar.gz -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJgC3alAAoJEMHgKYWVivCRgRAQAKXWpj0J+FcOAFLsVeM7WVa7 nbHGuAUALc8ogQ/x7HDcVgGTneAljlrrMN0Nmmv5CToQcd5ltAnqyWzyVpYTlbJQ pJdAflFkh4cjeQs2QjYGJT15vjQMjsWpD4JW95g3ZwkOk2Odm5zIn9GN1+fWXr4Y sqpgtslMGAePFirqRtw+mQQf0UdGAiWKiyyuEUPKjtbkx+DEEIIVAm5ijIAp/z5G XkrUN0QVndheziKiqjwjdUkc6pbC/wGe5gdmveYRgu+izpnqyVQ5Sco91VFxpgAg QR+f+r3bhWNEymLWOMX1CQfNdweQzEZICDOIZlg7DfFDg/ZorBxHIqInPBGmTED2 aQbQkbWJh51iQH+3E3lNH4xuCO3bOtqoF311je9/lKunDNfKbgfdXvt6RD0jCYKe P1sf8RfZ1y6347sivlHyQeD7hWKA4YFlWJpcXoWDypV05O3elIJOkmF/yVNJt6iM xBx8cF1yf18lAzVqUyM4piEQ57GnKPRvKUrBk+XjOIG9fH+SCfeeq7eWz5G9ul85 tXDho5ICsHe7+92Wh+ywFubhuW4Ia2KU6XYZojmtsKQQKW2yxCohUgcJf3ElYzOu pq3VzrBb9VU6iNiilDSZIpTW3kXu5OUn7V3RW9DuaimRmL3SrAUsJNo3ujKDfi2o ikYTd44sudivh3B9MyfD =2YsP -----END PGP SIGNATURE----- > -----Original Message----- > From: Jason Pyeron [mailto:jp...@pd...] > Sent: Friday, January 22, 2021 4:58 PM > To: log...@li... > Subject: [Logwatch-devel] release 7.5.5 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > SHA 256, 1, and MD5 sums for release 7.5.5 (git commit > a8bdb8ba8915339a5b2383b445cd8280aa88b637) > > cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5- > 1.noarch.rpm > fad38d6880db7f22196d160b0b83e52a124f7ced074a230316e90e905b12ce99 *logwatch-7.5.5-1.src.rpm > 138f181dea49470e1ef2d39af11b851aef0156500601312ce4de25d3a199b1c1 *logwatch-7.5.5.tar.gz > ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.rpm > b201a97d0fb467190456c8998dc8c9d61c65e971 *logwatch-7.5.5-1.src.rpm > f4e8ed4f846758be78b3d55791a867d70a197226 *logwatch-7.5.5.tar.gz > 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.rpm > 44654aec8e84c5c6ef2754bc0acaf6fa *logwatch-7.5.5-1.src.rpm > b658e4db27d905151396ecadcbcb24b1 *logwatch-7.5.5.tar.gz > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBAgAGBQJgC0pFAAoJEBA+OntaaKB7OhAP/0DivXXmQj7QELCYerg9/h0i > YKlx9e77ZbOhQyqa3pgUFFXYBB+FTZW12MxWcAI1hJ/eky03sUBif7cFxajb4GjZ > 6y80p5eJQFb8o5mo+dCHX1TPjO63GNLHdzbmx3jcbG6TU6BWlQlY9EO+GzxBGNwt > I2sjJhJFy6EYz2JbseffQvNGS94u81dLxitJineRw2AYzZ3q5OMPWUwkzHP+9mmz > Ng42xc3LzuIyZCJfmsoyvMEG9agoXNYqGoZ1kctuOSO1yBc+LGkmVEeg3T9zbzRu > vtXBWT6RrfQWGJUdz8393vtR4XiqneIFDoNAp3Gc68Iy9kbLCk9WrItHk7ljI3GN > RWSjpr1/udlaFSgwlVfl8am+Lno/JGmpEUOqAdp0e7BLqMqJ11RWA9RtVRWzvHbM > DLE2TQKGxF8CDoCnmhhOjqLZeXICn7dTPCFtDGCC/jEXvUACMkGNMx/Okl7SL7uo > qxFrth0MeOIIIJbrDGX2nO8wJFE6Pl3PE+9jCqdCO9n9IFbIsx9ipeVb131esth6 > qizPMUmueslxy2lc0vzzxg2YX/gOAbivmArfW5Lb6rBStR2wotPMzxAG8mRBHGfM > iFRwfe0g0J//YK3CeUoVzJCtoZ+PlRPI++JNYPz6BpGXwlT1EJ4Gh/5z9dh8YjWV > OhgHVAo3hcd/EiR5QtQz > =1DuD > -----END PGP SIGNATURE----- > > > > -----Original Message----- > > From: Jason Pyeron <jp...@pd...> > > Sent: Friday, January 22, 2021 2:47 PM > > To: 'log...@li...' <log...@li...> > > Subject: My new GPG key 0xC1E02985958AF091 / 0x958AF091 > > > > pub 4096R/958AF091 2021-01-22 [expires: 2024-01-22] > > uid Jason Pyeron <jp...@pd...> > > > > pub 4096R/C1E02985958AF091 2021-01-22 [expires: 2024-01-22] > > uid Jason Pyeron <jp...@pd...> > > > > $ gpg --export -a 958AF091 > > -----BEGIN PGP PUBLIC KEY BLOCK----- > > > > mQINBGALKesBEADw+FbnCEDqG1mvddC0KaDzxOJIo+cCa31nY4kDUyaaBVQzNNMT > > A/U1re7pJmxtT/k+BxAXJGw1VW+49Prxb4yGM0e484rsSkOAGTfhlhKATE8csS25 > > tRppeSqvTGbWG64DJWa1iKde6xOoFWS8osl382ErCIZjsery7SYKCLSTq9mmvOHM > > yjMhii1oncQo7zQP/KlDlla7B83KHCR2LH7jhNFNvr1UN5GYYNV4ITQtpxUpiiZ0 > > mjC96FBbX6lRsMkJDOx1G7e42ik26rUYGfpQUai68gnWSoPE/vZz/i0taFqClZ2c > > LYQ4sDoU06akVmhhvVUczd5ksPMUylAqjBcaIfU2r0CmsGPBRYMi76WCD4F8Ejjf > > tSjD/NTJ97oIJzg4nPoYPDaB4+9GfGmFUmS0+SzJeXnE5tAPIUfL90XrJggeS3re > > 9vmLZSG+fp5iZoW4MnyyLFvvoBy1RBsG/tZiQtIfz6/FT7zniymuPb/7VNuDRRMj > > zhSMQdHbNifaZjGwHXIlcNen6g5TjfHvUVcawr9dSJK4TpVxjPc1kmY6/8Xssx97 > > ycm1yxSYb2QPrcQxkCMC/fmHx7eyKeY8tow3TGevfDOHaSEkCGZuQ2V4961DEl0x > > SC9hQ9bSe2aju2U/dzAApaOnlSKoyHnBFGoZGqGwJGrignXl9AcVK0n0IQARAQAB > > tB9KYXNvbiBQeWVyb24gPGpweWVyb25AcGRpbmMudXM+iQI+BBMBAgAoBQJgCynr > > AhsDBQkFo5qABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDB4CmFlYrwkVAK > > EADhQWU6CalYil5TBl8B1CQXKcD56d9msqm2iptV9oC2ap40VCjG4axMYwXhYJQw > > FP8owN02m1fxI7BBKOOnhfklDdxQe87cQzajV0jTCI13/7AYf5/RMFWpetNFqU/n > > HhNxjCo9tIW9MUVM/1nNTRFwGyl/QXTqTfwRkIbRznMPCR2AhA84qjPOkOGgzFkE > > Q+abjLac0cY12JRblJTIqttOenHwXpkcjTbmP0Rk0PDdsXP6K9UgniVr/DhdFrh0 > > xnEVfWYRh4nP7qSKosAPJFkDQZzyUcTsW5kZ044bVMYhzmrhokzJ4E+dNzkdUMp7 > > 2ggdzlmr5s6SttmkrHYBWhsj4gWC3CngunR1H3uUWG6EFpnnLnqhLVCnZ4ONamnC > > x/Ztv+D7FQq+/xgM+qepRusfCjyunmPjn0PUlyApfD5pXBhupQdvA/N/4MRLgxej > > v5eTKPSYKQ74y7w0+Mt2wchON5PMX2IK/ydw4SSgRlomblfS3gmIUA9DM5uC++8p > > NzzqoJzY9+AqnU/kKAVlsoLWs5HZY8g5x0diFtKX1leItA4frlbDIY7HYO/P2GYo > > e7jnnV3HPbE8/bahOInA+qYUj278pAJIyLig9lHanVQO/3Wm5EbFJGSTaK/u0KCj > > tpUhs+BRnvVuELZta023HBKQFJgqNRYrGUAUdLATcmpC2LkCDQRgCynrARAAq5wr > > 2grss7bEPQ6qN0jpec9HBQDznt/6cqps1uhELsR30rI0exlK3ps7SjS1eXotw9w1 > > FL7Jj6PtVfaXkR5pxL4aL4NIfzHHsguQmQECrnjon0AOMRb2PFqLTAR2seQpTy5i > > xHOIbxEzurEygphfajfa04CwNtaMAPfoAAWMO3GlhcKkzvjBpUllKvf7GFNKC1i1 > > +XuHjEdetKNtlQbTkLUNmTvoCj6wYOCShHlyfi6X5/8l7YUFRLdtz18rIKSyG0j/ > > +CtoZ+Wn+5igObTa6AwLn39eRg3tWAFIvf4/0jgu1j3d5vTwgikFFNQHU7+zbrlP > > ilSKI6Ne5JBBWDjXR5K8a/7bOHQRT9lO431sWwVN/+m91ZPr56yYv141rGIj67eI > > +9ISBgM6PhPQx8SsJ00FlllkVDSAHmKXNFDUqSbCpu/MY6RL8/3+5nURbiYK/wYM > > GwAdg39/P2nrsAWj5x+itaLlp70mjstGXhY80+5M5omwDA/lCxmKiP+Td8lHw/OO > > 6jmJUPLrIPraBfgjlVrw/ulXGX4UlQvgjMD7WsKcI8ZEmCweIX0BNyS2dnqIGKaR > > L2JnTmBQtD7j32JvSLTOuz9qr/2xjW6IWlFqeu4pWTY22phDmSPw1Ar+0OQa46GH > > byxdvtivx5GCLowNXFfMEhEfAinIUdAhW3xFZE0AEQEAAYkCJQQYAQIADwUCYAsp > > 6wIbDAUJBaOagAAKCRDB4CmFlYrwkbZjD/9L2hOORxzXv6xgnZgMsha2hQWCuggY > > jdgRCb+qq09PyWzaz/CtYAQh3ooLSAXGYI9NGuNVlEdJ1FWiWNOOw5yOu7aO055w > > KczBG67N+d1VKB1b9OKv+6btYYi5tptuPuCMmfhggSt/VbsVUTClviKfysxnSfwL > > NU3lA/fr5E4zZjaWKc9evmXLd7/gbIqlGu/LwgT8I8QWZu9+nl2MG42SELIW5K17 > > n/BqnBf0VdtAPi1EeenCs+0/g/tnOSdM/n1DvS9dOWRvpcUaA2LQDv49lg4U/K+N > > 7yRGiVNt5GE8qMAu8rNvAptPB6LUGa0jfpcW/Vdf4F2e+KblwLhluZPu95xXk/Y9 > > nGGBCj8mq7Ed5WmU7lC6kfZNsyJuk0xvCZzeuvIc2rQTefrfadzAMoV87U9U5QF2 > > FAJc2OVh1L5ds9HZoear6ykdPz++s/zVQy/sjJSjdQB2AHl4+cHdp30S4FM9jPW9 > > aUxXcJw6ZlHCpTnWzBfamDAsnqSlSORucP3rs1h9iGrGplaMyasP/ARIA2+isXaO > > tuQyi1Q8AxhXfRsA12CqHVhIuSpPWmv07kCHGNO1EHplZOEBgLGfrDliz3clfrxH > > DqS36k8r99pvCyX8bepEI06D/q1HqCRPCx9lm/eVNh2iDAPB0D9l1XJyNTZ2o6wL > > 0j5dSmw2RjRuHA== > > =Tfro > > -----END PGP PUBLIC KEY BLOCK----- > > > > This replaces an expired in 2017-01-18 key: 0x8D6B5984DA0848AD > > > > -- > > Jason Pyeron | Architect > > PD Inc | > > 10 w 24th St | > > Baltimore, MD | > > > > .mil: jas...@ma... > > .com: jp...@pd... > > tel : 202-741-9397 > > |
|
From: Jason P. <jp...@pd...> - 2021-01-22 21:58:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SHA 256, 1, and MD5 sums for release 7.5.5 (git commit a8bdb8ba8915339a5b2383b445cd8280aa88b637) cbc8135d6a26347bf76a73f1aef231fbfaad0ea466501cadc72f2e9e0c30902a *logwatch-7.5.5-1.noarch.rpm fad38d6880db7f22196d160b0b83e52a124f7ced074a230316e90e905b12ce99 *logwatch-7.5.5-1.src.rpm 138f181dea49470e1ef2d39af11b851aef0156500601312ce4de25d3a199b1c1 *logwatch-7.5.5.tar.gz ef0c25b27e8052dd33ee8525f1381070fa1f6e42 *logwatch-7.5.5-1.noarch.rpm b201a97d0fb467190456c8998dc8c9d61c65e971 *logwatch-7.5.5-1.src.rpm f4e8ed4f846758be78b3d55791a867d70a197226 *logwatch-7.5.5.tar.gz 15080999622b5a7ec587f8d8ba3611e5 *logwatch-7.5.5-1.noarch.rpm 44654aec8e84c5c6ef2754bc0acaf6fa *logwatch-7.5.5-1.src.rpm b658e4db27d905151396ecadcbcb24b1 *logwatch-7.5.5.tar.gz -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJgC0pFAAoJEBA+OntaaKB7OhAP/0DivXXmQj7QELCYerg9/h0i YKlx9e77ZbOhQyqa3pgUFFXYBB+FTZW12MxWcAI1hJ/eky03sUBif7cFxajb4GjZ 6y80p5eJQFb8o5mo+dCHX1TPjO63GNLHdzbmx3jcbG6TU6BWlQlY9EO+GzxBGNwt I2sjJhJFy6EYz2JbseffQvNGS94u81dLxitJineRw2AYzZ3q5OMPWUwkzHP+9mmz Ng42xc3LzuIyZCJfmsoyvMEG9agoXNYqGoZ1kctuOSO1yBc+LGkmVEeg3T9zbzRu vtXBWT6RrfQWGJUdz8393vtR4XiqneIFDoNAp3Gc68Iy9kbLCk9WrItHk7ljI3GN RWSjpr1/udlaFSgwlVfl8am+Lno/JGmpEUOqAdp0e7BLqMqJ11RWA9RtVRWzvHbM DLE2TQKGxF8CDoCnmhhOjqLZeXICn7dTPCFtDGCC/jEXvUACMkGNMx/Okl7SL7uo qxFrth0MeOIIIJbrDGX2nO8wJFE6Pl3PE+9jCqdCO9n9IFbIsx9ipeVb131esth6 qizPMUmueslxy2lc0vzzxg2YX/gOAbivmArfW5Lb6rBStR2wotPMzxAG8mRBHGfM iFRwfe0g0J//YK3CeUoVzJCtoZ+PlRPI++JNYPz6BpGXwlT1EJ4Gh/5z9dh8YjWV OhgHVAo3hcd/EiR5QtQz =1DuD -----END PGP SIGNATURE----- > -----Original Message----- > From: Jason Pyeron <jp...@pd...> > Sent: Friday, January 22, 2021 2:47 PM > To: 'log...@li...' <log...@li...> > Subject: My new GPG key 0xC1E02985958AF091 / 0x958AF091 > > pub 4096R/958AF091 2021-01-22 [expires: 2024-01-22] > uid Jason Pyeron <jp...@pd...> > > pub 4096R/C1E02985958AF091 2021-01-22 [expires: 2024-01-22] > uid Jason Pyeron <jp...@pd...> > > $ gpg --export -a 958AF091 > -----BEGIN PGP PUBLIC KEY BLOCK----- > > mQINBGALKesBEADw+FbnCEDqG1mvddC0KaDzxOJIo+cCa31nY4kDUyaaBVQzNNMT > A/U1re7pJmxtT/k+BxAXJGw1VW+49Prxb4yGM0e484rsSkOAGTfhlhKATE8csS25 > tRppeSqvTGbWG64DJWa1iKde6xOoFWS8osl382ErCIZjsery7SYKCLSTq9mmvOHM > yjMhii1oncQo7zQP/KlDlla7B83KHCR2LH7jhNFNvr1UN5GYYNV4ITQtpxUpiiZ0 > mjC96FBbX6lRsMkJDOx1G7e42ik26rUYGfpQUai68gnWSoPE/vZz/i0taFqClZ2c > LYQ4sDoU06akVmhhvVUczd5ksPMUylAqjBcaIfU2r0CmsGPBRYMi76WCD4F8Ejjf > tSjD/NTJ97oIJzg4nPoYPDaB4+9GfGmFUmS0+SzJeXnE5tAPIUfL90XrJggeS3re > 9vmLZSG+fp5iZoW4MnyyLFvvoBy1RBsG/tZiQtIfz6/FT7zniymuPb/7VNuDRRMj > zhSMQdHbNifaZjGwHXIlcNen6g5TjfHvUVcawr9dSJK4TpVxjPc1kmY6/8Xssx97 > ycm1yxSYb2QPrcQxkCMC/fmHx7eyKeY8tow3TGevfDOHaSEkCGZuQ2V4961DEl0x > SC9hQ9bSe2aju2U/dzAApaOnlSKoyHnBFGoZGqGwJGrignXl9AcVK0n0IQARAQAB > tB9KYXNvbiBQeWVyb24gPGpweWVyb25AcGRpbmMudXM+iQI+BBMBAgAoBQJgCynr > AhsDBQkFo5qABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDB4CmFlYrwkVAK > EADhQWU6CalYil5TBl8B1CQXKcD56d9msqm2iptV9oC2ap40VCjG4axMYwXhYJQw > FP8owN02m1fxI7BBKOOnhfklDdxQe87cQzajV0jTCI13/7AYf5/RMFWpetNFqU/n > HhNxjCo9tIW9MUVM/1nNTRFwGyl/QXTqTfwRkIbRznMPCR2AhA84qjPOkOGgzFkE > Q+abjLac0cY12JRblJTIqttOenHwXpkcjTbmP0Rk0PDdsXP6K9UgniVr/DhdFrh0 > xnEVfWYRh4nP7qSKosAPJFkDQZzyUcTsW5kZ044bVMYhzmrhokzJ4E+dNzkdUMp7 > 2ggdzlmr5s6SttmkrHYBWhsj4gWC3CngunR1H3uUWG6EFpnnLnqhLVCnZ4ONamnC > x/Ztv+D7FQq+/xgM+qepRusfCjyunmPjn0PUlyApfD5pXBhupQdvA/N/4MRLgxej > v5eTKPSYKQ74y7w0+Mt2wchON5PMX2IK/ydw4SSgRlomblfS3gmIUA9DM5uC++8p > NzzqoJzY9+AqnU/kKAVlsoLWs5HZY8g5x0diFtKX1leItA4frlbDIY7HYO/P2GYo > e7jnnV3HPbE8/bahOInA+qYUj278pAJIyLig9lHanVQO/3Wm5EbFJGSTaK/u0KCj > tpUhs+BRnvVuELZta023HBKQFJgqNRYrGUAUdLATcmpC2LkCDQRgCynrARAAq5wr > 2grss7bEPQ6qN0jpec9HBQDznt/6cqps1uhELsR30rI0exlK3ps7SjS1eXotw9w1 > FL7Jj6PtVfaXkR5pxL4aL4NIfzHHsguQmQECrnjon0AOMRb2PFqLTAR2seQpTy5i > xHOIbxEzurEygphfajfa04CwNtaMAPfoAAWMO3GlhcKkzvjBpUllKvf7GFNKC1i1 > +XuHjEdetKNtlQbTkLUNmTvoCj6wYOCShHlyfi6X5/8l7YUFRLdtz18rIKSyG0j/ > +CtoZ+Wn+5igObTa6AwLn39eRg3tWAFIvf4/0jgu1j3d5vTwgikFFNQHU7+zbrlP > ilSKI6Ne5JBBWDjXR5K8a/7bOHQRT9lO431sWwVN/+m91ZPr56yYv141rGIj67eI > +9ISBgM6PhPQx8SsJ00FlllkVDSAHmKXNFDUqSbCpu/MY6RL8/3+5nURbiYK/wYM > GwAdg39/P2nrsAWj5x+itaLlp70mjstGXhY80+5M5omwDA/lCxmKiP+Td8lHw/OO > 6jmJUPLrIPraBfgjlVrw/ulXGX4UlQvgjMD7WsKcI8ZEmCweIX0BNyS2dnqIGKaR > L2JnTmBQtD7j32JvSLTOuz9qr/2xjW6IWlFqeu4pWTY22phDmSPw1Ar+0OQa46GH > byxdvtivx5GCLowNXFfMEhEfAinIUdAhW3xFZE0AEQEAAYkCJQQYAQIADwUCYAsp > 6wIbDAUJBaOagAAKCRDB4CmFlYrwkbZjD/9L2hOORxzXv6xgnZgMsha2hQWCuggY > jdgRCb+qq09PyWzaz/CtYAQh3ooLSAXGYI9NGuNVlEdJ1FWiWNOOw5yOu7aO055w > KczBG67N+d1VKB1b9OKv+6btYYi5tptuPuCMmfhggSt/VbsVUTClviKfysxnSfwL > NU3lA/fr5E4zZjaWKc9evmXLd7/gbIqlGu/LwgT8I8QWZu9+nl2MG42SELIW5K17 > n/BqnBf0VdtAPi1EeenCs+0/g/tnOSdM/n1DvS9dOWRvpcUaA2LQDv49lg4U/K+N > 7yRGiVNt5GE8qMAu8rNvAptPB6LUGa0jfpcW/Vdf4F2e+KblwLhluZPu95xXk/Y9 > nGGBCj8mq7Ed5WmU7lC6kfZNsyJuk0xvCZzeuvIc2rQTefrfadzAMoV87U9U5QF2 > FAJc2OVh1L5ds9HZoear6ykdPz++s/zVQy/sjJSjdQB2AHl4+cHdp30S4FM9jPW9 > aUxXcJw6ZlHCpTnWzBfamDAsnqSlSORucP3rs1h9iGrGplaMyasP/ARIA2+isXaO > tuQyi1Q8AxhXfRsA12CqHVhIuSpPWmv07kCHGNO1EHplZOEBgLGfrDliz3clfrxH > DqS36k8r99pvCyX8bepEI06D/q1HqCRPCx9lm/eVNh2iDAPB0D9l1XJyNTZ2o6wL > 0j5dSmw2RjRuHA== > =Tfro > -----END PGP PUBLIC KEY BLOCK----- > > This replaces an expired in 2017-01-18 key: 0x8D6B5984DA0848AD > > -- > Jason Pyeron | Architect > PD Inc | > 10 w 24th St | > Baltimore, MD | > > .mil: jas...@ma... > .com: jp...@pd... > tel : 202-741-9397 > |
|
From: Jason P. <jp...@pd...> - 2021-01-22 20:06:01
|
pub 4096R/958AF091 2021-01-22 [expires: 2024-01-22] uid Jason Pyeron <jp...@pd...> pub 4096R/C1E02985958AF091 2021-01-22 [expires: 2024-01-22] uid Jason Pyeron <jp...@pd...> $ gpg --export -a 958AF091 -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBGALKesBEADw+FbnCEDqG1mvddC0KaDzxOJIo+cCa31nY4kDUyaaBVQzNNMT A/U1re7pJmxtT/k+BxAXJGw1VW+49Prxb4yGM0e484rsSkOAGTfhlhKATE8csS25 tRppeSqvTGbWG64DJWa1iKde6xOoFWS8osl382ErCIZjsery7SYKCLSTq9mmvOHM yjMhii1oncQo7zQP/KlDlla7B83KHCR2LH7jhNFNvr1UN5GYYNV4ITQtpxUpiiZ0 mjC96FBbX6lRsMkJDOx1G7e42ik26rUYGfpQUai68gnWSoPE/vZz/i0taFqClZ2c LYQ4sDoU06akVmhhvVUczd5ksPMUylAqjBcaIfU2r0CmsGPBRYMi76WCD4F8Ejjf tSjD/NTJ97oIJzg4nPoYPDaB4+9GfGmFUmS0+SzJeXnE5tAPIUfL90XrJggeS3re 9vmLZSG+fp5iZoW4MnyyLFvvoBy1RBsG/tZiQtIfz6/FT7zniymuPb/7VNuDRRMj zhSMQdHbNifaZjGwHXIlcNen6g5TjfHvUVcawr9dSJK4TpVxjPc1kmY6/8Xssx97 ycm1yxSYb2QPrcQxkCMC/fmHx7eyKeY8tow3TGevfDOHaSEkCGZuQ2V4961DEl0x SC9hQ9bSe2aju2U/dzAApaOnlSKoyHnBFGoZGqGwJGrignXl9AcVK0n0IQARAQAB tB9KYXNvbiBQeWVyb24gPGpweWVyb25AcGRpbmMudXM+iQI+BBMBAgAoBQJgCynr AhsDBQkFo5qABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDB4CmFlYrwkVAK EADhQWU6CalYil5TBl8B1CQXKcD56d9msqm2iptV9oC2ap40VCjG4axMYwXhYJQw FP8owN02m1fxI7BBKOOnhfklDdxQe87cQzajV0jTCI13/7AYf5/RMFWpetNFqU/n HhNxjCo9tIW9MUVM/1nNTRFwGyl/QXTqTfwRkIbRznMPCR2AhA84qjPOkOGgzFkE Q+abjLac0cY12JRblJTIqttOenHwXpkcjTbmP0Rk0PDdsXP6K9UgniVr/DhdFrh0 xnEVfWYRh4nP7qSKosAPJFkDQZzyUcTsW5kZ044bVMYhzmrhokzJ4E+dNzkdUMp7 2ggdzlmr5s6SttmkrHYBWhsj4gWC3CngunR1H3uUWG6EFpnnLnqhLVCnZ4ONamnC x/Ztv+D7FQq+/xgM+qepRusfCjyunmPjn0PUlyApfD5pXBhupQdvA/N/4MRLgxej v5eTKPSYKQ74y7w0+Mt2wchON5PMX2IK/ydw4SSgRlomblfS3gmIUA9DM5uC++8p NzzqoJzY9+AqnU/kKAVlsoLWs5HZY8g5x0diFtKX1leItA4frlbDIY7HYO/P2GYo e7jnnV3HPbE8/bahOInA+qYUj278pAJIyLig9lHanVQO/3Wm5EbFJGSTaK/u0KCj tpUhs+BRnvVuELZta023HBKQFJgqNRYrGUAUdLATcmpC2LkCDQRgCynrARAAq5wr 2grss7bEPQ6qN0jpec9HBQDznt/6cqps1uhELsR30rI0exlK3ps7SjS1eXotw9w1 FL7Jj6PtVfaXkR5pxL4aL4NIfzHHsguQmQECrnjon0AOMRb2PFqLTAR2seQpTy5i xHOIbxEzurEygphfajfa04CwNtaMAPfoAAWMO3GlhcKkzvjBpUllKvf7GFNKC1i1 +XuHjEdetKNtlQbTkLUNmTvoCj6wYOCShHlyfi6X5/8l7YUFRLdtz18rIKSyG0j/ +CtoZ+Wn+5igObTa6AwLn39eRg3tWAFIvf4/0jgu1j3d5vTwgikFFNQHU7+zbrlP ilSKI6Ne5JBBWDjXR5K8a/7bOHQRT9lO431sWwVN/+m91ZPr56yYv141rGIj67eI +9ISBgM6PhPQx8SsJ00FlllkVDSAHmKXNFDUqSbCpu/MY6RL8/3+5nURbiYK/wYM GwAdg39/P2nrsAWj5x+itaLlp70mjstGXhY80+5M5omwDA/lCxmKiP+Td8lHw/OO 6jmJUPLrIPraBfgjlVrw/ulXGX4UlQvgjMD7WsKcI8ZEmCweIX0BNyS2dnqIGKaR L2JnTmBQtD7j32JvSLTOuz9qr/2xjW6IWlFqeu4pWTY22phDmSPw1Ar+0OQa46GH byxdvtivx5GCLowNXFfMEhEfAinIUdAhW3xFZE0AEQEAAYkCJQQYAQIADwUCYAsp 6wIbDAUJBaOagAAKCRDB4CmFlYrwkbZjD/9L2hOORxzXv6xgnZgMsha2hQWCuggY jdgRCb+qq09PyWzaz/CtYAQh3ooLSAXGYI9NGuNVlEdJ1FWiWNOOw5yOu7aO055w KczBG67N+d1VKB1b9OKv+6btYYi5tptuPuCMmfhggSt/VbsVUTClviKfysxnSfwL NU3lA/fr5E4zZjaWKc9evmXLd7/gbIqlGu/LwgT8I8QWZu9+nl2MG42SELIW5K17 n/BqnBf0VdtAPi1EeenCs+0/g/tnOSdM/n1DvS9dOWRvpcUaA2LQDv49lg4U/K+N 7yRGiVNt5GE8qMAu8rNvAptPB6LUGa0jfpcW/Vdf4F2e+KblwLhluZPu95xXk/Y9 nGGBCj8mq7Ed5WmU7lC6kfZNsyJuk0xvCZzeuvIc2rQTefrfadzAMoV87U9U5QF2 FAJc2OVh1L5ds9HZoear6ykdPz++s/zVQy/sjJSjdQB2AHl4+cHdp30S4FM9jPW9 aUxXcJw6ZlHCpTnWzBfamDAsnqSlSORucP3rs1h9iGrGplaMyasP/ARIA2+isXaO tuQyi1Q8AxhXfRsA12CqHVhIuSpPWmv07kCHGNO1EHplZOEBgLGfrDliz3clfrxH DqS36k8r99pvCyX8bepEI06D/q1HqCRPCx9lm/eVNh2iDAPB0D9l1XJyNTZ2o6wL 0j5dSmw2RjRuHA== =Tfro -----END PGP PUBLIC KEY BLOCK----- This replaces an expired in 2017-01-18 key: 0x8D6B5984DA0848AD -- Jason Pyeron | Architect PD Inc | 10 w 24th St | Baltimore, MD | .mil: jas...@ma... .com: jp...@pd... tel : 202-741-9397 |
|
From: Sophie L. <so...@kl...> - 2020-11-15 07:13:26
|
Me neither! On 15 Nov 2020, at 3:51 am, Jason Pyeron <jp...@pd...> wrote: > > -----Original Message----- > From: Bjorn via Logwatch-devel <log...@li...> > Sent: Saturday, November 14, 2020 8:37 PM > To: log...@li... ... > - This logwatch-devel mailing list is deprecated. For future reference, > it is better to use either the "discussion" list or the "tickets" list > under sourceforge.net. For example: > https://sourceforge.net/p/logwatch/discussion/ Did not know that... _______________________________________________ Logwatch-devel mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/logwatch-devel |
|
From: Jason P. <jp...@pd...> - 2020-11-15 02:50:21
|
> -----Original Message----- > From: Bjorn via Logwatch-devel <log...@li...> > Sent: Saturday, November 14, 2020 8:37 PM > To: log...@li... ... > - This logwatch-devel mailing list is deprecated. For future reference, > it is better to use either the "discussion" list or the "tickets" list > under sourceforge.net. For example: > https://sourceforge.net/p/logwatch/discussion/ Did not know that... |
|
From: Bjorn <bj...@us...> - 2020-11-15 01:37:23
|
Some observations: - The first item is probably innocuous. The "null" request (no URL) was removed from the script a couple years ago because of the many false positives, so you should update to the current version. I'll note that the response code was 200, which is a successful response. I'd be interested in knowing if it should not have been successful. - For the requests with error response codes, look for a line that has "GET / HTTP" in either the access_log or the ssl_request_log (or any other log files your system uses). - Similarly for the other accesses. The "/0bef" string would seem very distinctive. - On an open web server, it is usual to find attempted accesses from other unknown systems. The GET mentioned above is only one method, but the most common one when other systems probe your server. - Using "tail" would only find more recent accesses, and "tail -f" would only find future log statements; better to just "grep" the log files directly. - For the accesses with error response code 400, your system would not have served valid data, and therefore should not have any other meaningful effect on your system. - This logwatch-devel mailing list is deprecated. For future reference, it is better to use either the "discussion" list or the "tickets" list under sourceforge.net. For example: https://sourceforge.net/p/logwatch/discussion/ On 11/14/20 3:00 PM, Dave at Collaboration Café wrote: > Hi, I am running an Ubuntu 18.04 Nginx-powered server with multiple > vhosts, with Logwatch giving me a report (highest level of detail) in my > mailbox every morning. > > In the httpd section of the report, I'm frequently getting the snippet > below. > > A total of 1 possible successful probes were detected (the following URLs > contain strings that match one or more of a listing of strings that > indicate a possible exploit): > > null HTTP Response 200 > > Then in the requests listing of the httpd section, I'm seeing output > such as below (this is just a small snippet of a day's report): > > Requests with error response codes > 400 Bad Request > /: 14 Time(s) > null: 8 Time(s) > /0bef: 6 Time(s) > > Question 1: has anyone seen this before, and do I have a serious > problem? I'm not noticing anything amiss in my server's operation... > > Question 2: I have been trying to locate the exact log lines in > /var/log/nginx/access.log and /var/log/nginx/error.log by manually > tailing my logs and by using grep to search. But so far I have failed. > Can anyone advise me of a way to locate these lines effectively? > > Any other useful advice would be much appreciated. > |
|
From: Dave at C. C. <da...@co...> - 2020-11-14 23:16:46
|
Hi, I am running an Ubuntu 18.04 Nginx-powered server with multiple
vhosts, with Logwatch giving me a report (highest level of detail) in my
mailbox every morning.
In the httpd section of the report, I'm frequently getting the snippet
below.
A total of 1 possible successful probes were detected (the following
URLs
contain strings that match one or more of a listing of strings that
indicate a possible exploit):
null HTTP Response 200
Then in the requests listing of the httpd section, I'm seeing output
such as below (this is just a small snippet of a day's report):
Requests with error response codes
400 Bad Request
/: 14 Time(s)
null: 8 Time(s)
/0bef: 6 Time(s)
Question 1: has anyone seen this before, and do I have a serious
problem? I'm not noticing anything amiss in my server's operation...
Question 2: I have been trying to locate the exact log lines in
/var/log/nginx/access.log and /var/log/nginx/error.log by manually
tailing my logs and by using grep to search. But so far I have failed.
Can anyone advise me of a way to locate these lines effectively?
Any other useful advice would be much appreciated.
--
With all best wishes,
Dave
--
With all best wishes,
Dave
|
|
From: Frank C. <fr...@cr...> - 2020-10-21 11:12:20
|
Yes, looking through a few of the scripts, their use of lc is reasonable, e.g. to sort into a reasonable order or to do a consistent check for keywords, but it is very likely that there are more significant issues within the core itself. So, we probably need to look and see what the real requirements are for each use and then consider if it makes sense. Frank On Tue, 2020-10-20 at 13:10 -0700, Bjorn via Logwatch-devel wrote: > I am pretty sure it was well before that 2006 date. I assumed it was > a > decision from the initial creation of logwatch, well before my (and > probably your) initial involvement. > > Indeed, the main stumbling blocks are backwards compatibility > (minimize > breaking existing logwatch deployments), and testing. We don't have > a > test suite, and most servers probably exercise only a small fraction > of > the overall logwatch code base. > > Of the list of files you sent, the services have the most occurrences > of > 'lc', but I believe that the configuration files (both default and > user-defined) are where the most problems would occur. Because most > declared names and values are lower-cased when read by logwatch. > > > On 10/20/20 11:38 AM, Mike Tremaine wrote: > > I think.. It happened back around 2006 on move from 7.0 to 7.1 > > > > I see this email exchange in my folder > > > > > On Tue, 2006-01-17 at 22:41 -0500, Aaron Weeks wrote: > > > > > > > > Also, I've noticed in the 7.1 and 7.2 releases, that at some > > > > > point, > > > > > logfiles will get changed to lowercase. I am trying to write > > > > > a filter > > > > > for oracle, and my oracle alert logs have uppercase letters > > > > > in the > > > > > paths. Is the shifting to lowercase intentional? If so, is > > > > > there a > > > > > way around it? > > > > > > > > This problem is still an issue. When the logfile name gets > > > > shifted to > > > > lowercase, it sees my log file as not existing. > > > > > > > > > > Use quotes around your log file names > > > > > > LogFile = "NAME" > > > > > > Otherwise everything gets lowercased. > > > > > > -Mike > > > > > > [We should put that in the HOWTO ;) ] > > > > > > I also see some early issues with the HTTP module and the Exploits > > file. I do not remember doing this so I doubt I added the lowercase > > code but it was a long time ago. I think it can be removed BUT > > there would have to be a lot testing to see what breaks when you do > > it. Just my 2 cent opinion. > > > > -Mike > > > > > > > On Oct 20, 2020, at 11:27 AM, Orion Poplawski < > > > or...@nw... > > > > wrote: > > > > > > Folks - > > > > > > It's becoming past ridiculous that logwatch lowercases > > > everything in the > > > configuration files. I'm afraid I never understood the reason > > > for it. > > > Perhaps someone with a longer experience with logwatch can tell > > > me? > > > > > > But the latest issue is with sudo's ignore_commands - and this > > > is important > > > since different cased commands could conceivably be quite > > > different. > > > > > > So, what are the ramifications of no longer lower-casing > > > everything? > > > > > > Orion > > > > > > -- > > > Orion Poplawski > > > Manager of NWRA Technical Systems 720-772-5637 > > > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > > > 3380 Mitchell Lane > > > or...@nw... > > > > > > Boulder, CO 80301 > > > https://www.nwra.com/ > > > > > > > > > > > > _______________________________________________ > > > Logwatch-devel mailing list > > > Log...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > > > > > > > > > > > _______________________________________________ > > Logwatch-devel mailing list > > Log...@li... > > > > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > > > > > > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > |
|
From: Bjorn <bj...@us...> - 2020-10-20 20:42:08
|
I am pretty sure it was well before that 2006 date. I assumed it was a decision from the initial creation of logwatch, well before my (and probably your) initial involvement. Indeed, the main stumbling blocks are backwards compatibility (minimize breaking existing logwatch deployments), and testing. We don't have a test suite, and most servers probably exercise only a small fraction of the overall logwatch code base. Of the list of files you sent, the services have the most occurrences of 'lc', but I believe that the configuration files (both default and user-defined) are where the most problems would occur. Because most declared names and values are lower-cased when read by logwatch. On 10/20/20 11:38 AM, Mike Tremaine wrote: > I think.. It happened back around 2006 on move from 7.0 to 7.1 > > I see this email exchange in my folder > >> On Tue, 2006-01-17 at 22:41 -0500, Aaron Weeks wrote: >> >>> >>>> Also, I've noticed in the 7.1 and 7.2 releases, that at some point, >>>> logfiles will get changed to lowercase. I am trying to write a filter >>>> for oracle, and my oracle alert logs have uppercase letters in the >>>> paths. Is the shifting to lowercase intentional? If so, is there a >>>> way around it? >>> >>> This problem is still an issue. When the logfile name gets shifted to >>> lowercase, it sees my log file as not existing. >>> >> >> Use quotes around your log file names >> >> LogFile = "NAME" >> >> Otherwise everything gets lowercased. >> >> -Mike >> >> [We should put that in the HOWTO ;) ] > > > I also see some early issues with the HTTP module and the Exploits file. I do not remember doing this so I doubt I added the lowercase code but it was a long time ago. I think it can be removed BUT there would have to be a lot testing to see what breaks when you do it. Just my 2 cent opinion. > > -Mike > > >> On Oct 20, 2020, at 11:27 AM, Orion Poplawski <or...@nw...> wrote: >> >> Folks - >> >> It's becoming past ridiculous that logwatch lowercases everything in the >> configuration files. I'm afraid I never understood the reason for it. >> Perhaps someone with a longer experience with logwatch can tell me? >> >> But the latest issue is with sudo's ignore_commands - and this is important >> since different cased commands could conceivably be quite different. >> >> So, what are the ramifications of no longer lower-casing everything? >> >> Orion >> >> -- >> Orion Poplawski >> Manager of NWRA Technical Systems 720-772-5637 >> NWRA, Boulder/CoRA Office FAX: 303-415-9702 >> 3380 Mitchell Lane or...@nw... >> Boulder, CO 80301 https://www.nwra.com/ >> >> >> _______________________________________________ >> Logwatch-devel mailing list >> Log...@li... >> https://lists.sourceforge.net/lists/listinfo/logwatch-devel > > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > |
|
From: Orion P. <or...@nw...> - 2020-10-20 19:54:40
|
On 10/20/20 12:38 PM, Mike Tremaine wrote: > I think.. It happened back around 2006 on move from 7.0 to 7.1 > > I see this email exchange in my folder > >> On Tue, 2006-01-17 at 22:41 -0500, Aaron Weeks wrote: >> >>> >>>> Also, I've noticed in the 7.1 and 7.2 releases, that at some point, >>>> logfiles will get changed to lowercase. I am trying to write a filter >>>> for oracle, and my oracle alert logs have uppercase letters in the >>>> paths. Is the shifting to lowercase intentional? If so, is there a >>>> way around it? >>> >>> This problem is still an issue. When the logfile name gets shifted to >>> lowercase, it sees my log file as not existing. >>> >> >> Use quotes around your log file names >> >> LogFile = "NAME" >> >> Otherwise everything gets lowercased. >> >> -Mike >> >> [We should put that in the HOWTO ;) ] > > > I also see some early issues with the HTTP module and the Exploits file. I do not remember doing this so I doubt I added the lowercase code but it was a long time ago. I think it can be removed BUT there would have to be a lot testing to see what breaks when you do it. Just my 2 cent opinion. > > -Mike Thanks at least for this - quoting items in config files does allow for the case to be preserved, so this dramatically removes the urgency for me. But it still might be worth removing that altogether. Though we definitely need to document it! Orion > On Oct 20, 2020, at 11:27 AM, Orion Poplawski <or...@nw...> wrote: >> >> Folks - >> >> It's becoming past ridiculous that logwatch lowercases everything in the >> configuration files. I'm afraid I never understood the reason for it. >> Perhaps someone with a longer experience with logwatch can tell me? >> >> But the latest issue is with sudo's ignore_commands - and this is important >> since different cased commands could conceivably be quite different. >> >> So, what are the ramifications of no longer lower-casing everything? >> >> Orion >> >> -- >> Orion Poplawski >> Manager of NWRA Technical Systems 720-772-5637 >> NWRA, Boulder/CoRA Office FAX: 303-415-9702 >> 3380 Mitchell Lane or...@nw... >> Boulder, CO 80301 https://www.nwra.com/ >> >> >> _______________________________________________ >> Logwatch-devel mailing list >> Log...@li... >> https://lists.sourceforge.net/lists/listinfo/logwatch-devel > -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nw... Boulder, CO 80301 https://www.nwra.com/ |
|
From: Sophie L. <so...@kl...> - 2020-10-20 19:13:07
|
Do logwatch developers use case insensitive file systems? ^^ Lower casing file names is a nightmare. On 20 Oct 2020, at 8:52 pm, Mike Tremaine <mg...@st...> wrote: I think.. It happened back around 2006 on move from 7.0 to 7.1 I see this email exchange in my folder > On Tue, 2006-01-17 at 22:41 -0500, Aaron Weeks wrote: > >>> Also, I've noticed in the 7.1 and 7.2 releases, that at some point, >>> logfiles will get changed to lowercase. I am trying to write a filter >>> for oracle, and my oracle alert logs have uppercase letters in the >>> paths. Is the shifting to lowercase intentional? If so, is there a >>> way around it? >> This problem is still an issue. When the logfile name gets shifted to >> lowercase, it sees my log file as not existing. > > Use quotes around your log file names > > LogFile = "NAME" > > Otherwise everything gets lowercased. > > -Mike > > [We should put that in the HOWTO ;) ] I also see some early issues with the HTTP module and the Exploits file. I do not remember doing this so I doubt I added the lowercase code but it was a long time ago. I think it can be removed BUT there would have to be a lot testing to see what breaks when you do it. Just my 2 cent opinion. -Mike > On Oct 20, 2020, at 11:27 AM, Orion Poplawski <or...@nw...> wrote: > > Folks - > > It's becoming past ridiculous that logwatch lowercases everything in the > configuration files. I'm afraid I never understood the reason for it. > Perhaps someone with a longer experience with logwatch can tell me? > > But the latest issue is with sudo's ignore_commands - and this is important > since different cased commands could conceivably be quite different. > > So, what are the ramifications of no longer lower-casing everything? > > Orion > > -- > Orion Poplawski > Manager of NWRA Technical Systems 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nw... > Boulder, CO 80301 https://www.nwra.com/ > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel _______________________________________________ Logwatch-devel mailing list Log...@li... https://lists.sourceforge.net/lists/listinfo/logwatch-devel |
|
From: Mike T. <mg...@st...> - 2020-10-20 18:58:07
|
The biggest ramifications I can see is the Config files are written with with uppercase, I assume for style. But it’s everywhere
Detail = 10
TmpDir = /tmp
Archives = Yes
# You can also disable certain services (when specifying all)
Service = "-afpd”
In logwatch.pl there are 9 calls to lc these two are the ones that covert the config name / value pairs
push @ReadConfigNames, lc $name;
push @ReadConfigValues, getInt $value;
But over all these are files with lc in them (might be some false positives in the list) removing lc from the main script and pushing required calls down to the module level might be the way to go if you really want to remove it.
Rigel:scripts mgt$ grep -c -R lc . | grep -v ':0'
./logwatch.pl:9
./shared/journalctl:7
./shared/applyeurodate:2
./services/postgresql:3
./services/eximstats:1
./services/amavis:15
./services/fail2ban:1
./services/mailscanner:3
./services/dnf-rpm:8
./services/php:3
./services/evtsecurity:4
./services/http:5
./services/mysql:3
./services/citadel:12
./services/postfix:28
./services/slon:2
./services/iptables:2
./services/windows:1
./services/mdadm:2
./services/pam_unix:2
./services/sendmail:1
> On Oct 20, 2020, at 11:27 AM, Orion Poplawski <or...@nw...> wrote:
>
> Folks -
>
> It's becoming past ridiculous that logwatch lowercases everything in the
> configuration files. I'm afraid I never understood the reason for it.
> Perhaps someone with a longer experience with logwatch can tell me?
>
> But the latest issue is with sudo's ignore_commands - and this is important
> since different cased commands could conceivably be quite different.
>
> So, what are the ramifications of no longer lower-casing everything?
>
> Orion
>
> --
> Orion Poplawski
> Manager of NWRA Technical Systems 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane or...@nw...
> Boulder, CO 80301 https://www.nwra.com/
>
>
> _______________________________________________
> Logwatch-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logwatch-devel
|
|
From: Mike T. <mg...@st...> - 2020-10-20 18:51:31
|
I think.. It happened back around 2006 on move from 7.0 to 7.1 I see this email exchange in my folder > On Tue, 2006-01-17 at 22:41 -0500, Aaron Weeks wrote: > >> >>> Also, I've noticed in the 7.1 and 7.2 releases, that at some point, >>> logfiles will get changed to lowercase. I am trying to write a filter >>> for oracle, and my oracle alert logs have uppercase letters in the >>> paths. Is the shifting to lowercase intentional? If so, is there a >>> way around it? >> >> This problem is still an issue. When the logfile name gets shifted to >> lowercase, it sees my log file as not existing. >> > > Use quotes around your log file names > > LogFile = "NAME" > > Otherwise everything gets lowercased. > > -Mike > > [We should put that in the HOWTO ;) ] I also see some early issues with the HTTP module and the Exploits file. I do not remember doing this so I doubt I added the lowercase code but it was a long time ago. I think it can be removed BUT there would have to be a lot testing to see what breaks when you do it. Just my 2 cent opinion. -Mike > On Oct 20, 2020, at 11:27 AM, Orion Poplawski <or...@nw...> wrote: > > Folks - > > It's becoming past ridiculous that logwatch lowercases everything in the > configuration files. I'm afraid I never understood the reason for it. > Perhaps someone with a longer experience with logwatch can tell me? > > But the latest issue is with sudo's ignore_commands - and this is important > since different cased commands could conceivably be quite different. > > So, what are the ramifications of no longer lower-casing everything? > > Orion > > -- > Orion Poplawski > Manager of NWRA Technical Systems 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nw... > Boulder, CO 80301 https://www.nwra.com/ > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel |
|
From: Orion P. <or...@nw...> - 2020-10-20 18:27:44
|
Folks - It's becoming past ridiculous that logwatch lowercases everything in the configuration files. I'm afraid I never understood the reason for it. Perhaps someone with a longer experience with logwatch can tell me? But the latest issue is with sudo's ignore_commands - and this is important since different cased commands could conceivably be quite different. So, what are the ramifications of no longer lower-casing everything? Orion -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nw... Boulder, CO 80301 https://www.nwra.com/ |
|
From: Bjorn <bj...@us...> - 2020-09-12 17:44:14
|
Matthias, Try the attached patch. For future reference, the use of this mailing list is deprecated. It is best to file bugs/patches/requests under: https://sourceforge.net/p/logwatch/_list/tickets Bjorn On 9/12/20 2:37 AM, Matthias Fischer wrote: > Hi, > > currently we're using 'logwatch 7.5.4' on IPFire firewall systems. > > Considering the 'dhcp' entries, we're receiving bug reports about > logwatch logs containing unknown messages like this: > > [IPFire Bug List / > #12242](https://bugzilla.ipfire.org/show_bug.cgi?id=12242): > > Unknown Entries: > reuse_lease: lease age 0 (secs) under 25% threshold, reply with > unaltered, existing lease for 10.0.0.21: 1 Time(s) > reuse_lease: lease age 3 (secs) under 25% threshold, reply with > unaltered, existing lease for 10.0.0.27: 1 Time(s) > > Comment in https://community.ipfire.org/t/dhcp-server-unknown-entries/211: > "This seems to be the case while the dhcp server logs if a client asks > too early for a still existing lease. There is usally nothing wrong with > the network." > > Could this be fixed by altering 'logwatch-7.5.4\scripts\services\dhcpd'? > > Best, > Matthias Fischer > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > |
|
From: Matthias F. <mat...@ip...> - 2020-09-12 09:56:36
|
Hi, currently we're using 'logwatch 7.5.4' on IPFire firewall systems. Considering the 'dhcp' entries, we're receiving bug reports about logwatch logs containing unknown messages like this: [IPFire Bug List / #12242](https://bugzilla.ipfire.org/show_bug.cgi?id=12242): Unknown Entries: reuse_lease: lease age 0 (secs) under 25% threshold, reply with unaltered, existing lease for 10.0.0.21: 1 Time(s) reuse_lease: lease age 3 (secs) under 25% threshold, reply with unaltered, existing lease for 10.0.0.27: 1 Time(s) Comment in https://community.ipfire.org/t/dhcp-server-unknown-entries/211: "This seems to be the case while the dhcp server logs if a client asks too early for a still existing lease. There is usally nothing wrong with the network." Could this be fixed by altering 'logwatch-7.5.4\scripts\services\dhcpd'? Best, Matthias Fischer |
|
From: Bjorn <bj...@us...> - 2020-08-09 02:12:25
|
Unfortunately that change would break other Logwatch scripts, which in
many cases try to match a string as being at the beginning, after
stripping the date (and perhaps other items). Also, the letsencrypt log
format seems to break the standard syslog format, which does call for a
space after the date.
One way is to specify the string as an argument to the script. For
example, in your case add the following to the pertinent file in
/etc/logwatch/conf/logfiles:
*ApplyEuroDate = "%F %T,%L:"
instead of just *ApplyEurodate.
So you can customize it, without changing the script.
Two other items:
- Are you writing a script for letsencrypt logs? I don't think it
currently exists.
- The use of this email list is deprecated; the preferred method is
by using the discussion page at:
https://sourceforge.net/p/logwatch/discussion/
On 8/5/20 12:34 AM, Guillaume LEBAS wrote:
> Hello,
>
> Logwatch (v7.5.4 and below) uses a trailing space in "ApplyStdDate"
> and "ApplyEuroDate" (adapted from the former) formats. I struggled to
> figure out why it outputs nothing from Let's Encrypt logs, eg.
> "2020-08-02 21:12:16,231:DEBUG:certbot[...]".
>
> I suggest the following changes:
>
> diff --git a/logwatch-7.5.4/scripts/shared/applyeurodate
> b/logwatch-dev/scripts/shared/applyeurodate
> index 111c540..8c72ec3 100644
> --- a/logwatch-7.5.4/scripts/shared/applyeurodate
> +++ b/logwatch-dev/scripts/shared/applyeurodate
> @@ -30,7 +30,7 @@ use Logwatch ':dates';
>
> my $Debug = $ENV{'LOGWATCH_DEBUG'} || 0;
>
> -$SearchDate = TimeFilter($ARGV[0] || '%Y-%m-%d %H:%M:%S(,...)? ');
> +$SearchDate = TimeFilter($ARGV[0] || '%Y-%m-%d %H:%M:%S(,...)?');
>
> if ( $Debug > 5 ) {
> print STDERR "DEBUG: Inside ApplyEuroDate...\n";
> diff --git a/logwatch-7.5.4/scripts/shared/applystddate
> b/logwatch-dev/scripts/shared/applystddate
> index cc0bd06..e8f8439 100644
> --- a/logwatch-7.5.4/scripts/shared/applystddate
> +++ b/logwatch-dev/scripts/shared/applystddate
> @@ -24,8 +24,8 @@ my $Debug = $ENV{'LOGWATCH_DEBUG'} || 0;
>
> # customize the Timefilter by appending a string:
> # *ApplyStdDate = "%H:%M %d/%m/%Y"
> -$SearchDate = TimeFilter($ARGV[0] || '%b %e %H:%M:%S ');
> -$SearchDateRsyslog =
> TimeFilter('%Y-%m-%dT%H:%M:%S(:?\.[0-9]+)?(:?[+-][0-9]{2}:[0-9]{2}|Z) ');
> +$SearchDate = TimeFilter($ARGV[0] || '%b %e %H:%M:%S');
> +$SearchDateRsyslog =
> TimeFilter('%Y-%m-%dT%H:%M:%S(:?\.[0-9]+)?(:?[+-][0-9]{2}:[0-9]{2}|Z)');
>
> # The date might be "Dec 09", but it needs to be "Dec 9"...
> #$SearchDate =~ s/ 0/ /;
>
>
> Best regards.
>
>
> _______________________________________________
> Logwatch-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logwatch-devel
>
|
|
From: Guillaume L. <gui...@ou...> - 2020-08-05 07:34:47
|
Hello,
Logwatch (v7.5.4 and below) uses a trailing space in "ApplyStdDate" and "ApplyEuroDate" (adapted from the former) formats. I struggled to figure out why it outputs nothing from Let's Encrypt logs, eg. "2020-08-02 21:12:16,231:DEBUG:certbot[...]".
I suggest the following changes:
diff --git a/logwatch-7.5.4/scripts/shared/applyeurodate b/logwatch-dev/scripts/shared/applyeurodate
index 111c540..8c72ec3 100644
--- a/logwatch-7.5.4/scripts/shared/applyeurodate
+++ b/logwatch-dev/scripts/shared/applyeurodate
@@ -30,7 +30,7 @@ use Logwatch ':dates';
my $Debug = $ENV{'LOGWATCH_DEBUG'} || 0;
-$SearchDate = TimeFilter($ARGV[0] || '%Y-%m-%d %H:%M:%S(,...)? ');
+$SearchDate = TimeFilter($ARGV[0] || '%Y-%m-%d %H:%M:%S(,...)?');
if ( $Debug > 5 ) {
print STDERR "DEBUG: Inside ApplyEuroDate...\n";
diff --git a/logwatch-7.5.4/scripts/shared/applystddate b/logwatch-dev/scripts/shared/applystddate
index cc0bd06..e8f8439 100644
--- a/logwatch-7.5.4/scripts/shared/applystddate
+++ b/logwatch-dev/scripts/shared/applystddate
@@ -24,8 +24,8 @@ my $Debug = $ENV{'LOGWATCH_DEBUG'} || 0;
# customize the Timefilter by appending a string:
# *ApplyStdDate = "%H:%M %d/%m/%Y"
-$SearchDate = TimeFilter($ARGV[0] || '%b %e %H:%M:%S ');
-$SearchDateRsyslog = TimeFilter('%Y-%m-%dT%H:%M:%S(:?\.[0-9]+)?(:?[+-][0-9]{2}:[0-9]{2}|Z) ');
+$SearchDate = TimeFilter($ARGV[0] || '%b %e %H:%M:%S');
+$SearchDateRsyslog = TimeFilter('%Y-%m-%dT%H:%M:%S(:?\.[0-9]+)?(:?[+-][0-9]{2}:[0-9]{2}|Z)');
# The date might be "Dec 09", but it needs to be "Dec 9"...
#$SearchDate =~ s/ 0/ /;
Best regards.
|
|
From: Bjorn <bj...@us...> - 2020-05-11 16:35:48
|
Different distributions may use different paths, not only for the zfs utilities, but many other commands and log files. For the situation you describe, you can place the following two lines: $pathto_zpool = "/sbin/zpool" $pathto_zfs = "/sbin/zfs" in a file you create named: /etc/logwatch/conf/services/zz-zfs.conf These customizations are described in the HOWTO-Customize-LogWatch file. P.S. For future reference, this logwatch-devel mailing list is deprecated. It is best to file questions under: https://sourceforge.net/p/logwatch/discussion/ Bugs, patches, and requests go to: https://sourceforge.net/p/logwatch/_list/tickets On 5/10/20 2:23 PM, Stephen Sewell wrote: > Hey guys, > > My logwatch installation on Ubuntu wasn't sending me zfs information and > I finally tracked down the root cause yesterday. > > In zz-zfs the pathto_zpool and pathto_zfs environment variables default > to /usr/sbin unless they're overridden, but Ubuntu keeps its zfs > utilities in /sbin. > > It seems like all it really needs to do is something like this. > > if ( envDefined ) useEnv() > else if ( toolsInSbin ) useSbin() > else useUsrSbin() > > If you have any contributor guidelines, I'd be happy to fix it for you. > > > _______________________________________________ > Logwatch-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logwatch-devel > |