[clamav-users] [SUSPECTED SPAM] Re: ClamAV 0.103.0 rc2

[Micah Snyder (micasnyd)]

Kevin, Arjen, all:

If you're interested, we found the cause of the freshclam SysLog issue. The source ended up being an issue with our autotools build system and how we link freshclam.
If any of you are willing to try this patch, it'd be nice to hear how it goes. In our testing the patch solves the issue.

IMPORTANT:  Because this is a change to autotools, you'll have to test this on a machine with autoconf, automake, m4, libtool, and pkg-config installed and you'll have to run autogen.sh to regenerate the autotools stuff before running the build.

Patch follows:

diff --git a/freshclam/Makefile.am b/freshclam/Makefile.am
index 95f4d6c6b..ab6ac8f1c 100644
--- a/freshclam/Makefile.am
+++ b/freshclam/Makefile.am
@@ -35,7 +35,7 @@ endif
 AM_CFLAGS=@WERR_CFLAGS@
 DEFS = @DEFS@
 AM_CPPFLAGS = -I$(top_srcdir) -I$(top_srcdir)/shared -I$(top_srcdir)/libclamav -I$(top_builddir)/libclamav -I$(top_srcdir)/libclamunrar_iface -I$(top_srcdir)/libfreshclam @CURL_CPPFLAGS@ @SSL_CPPFLAGS@ @FRESHCLAM_CPPFLAGS@ @ZLIB_CFLAGS@ @JSON_CPPFLAGS@ @PCRE_CPPFLAGS@
-LIBS = @SSL_LDFLAGS@ @SSL_LIBS@ @CURL_LDFLAGS@ @CURL_LIBS@ $(top_builddir)/libclamav/libclamav.la $(top_builddir)/shared/libshared.la $(top_builddir)/libfreshclam/libfreshclam.la @FRESHCLAM_LIBS@ @ZLIB_LIBS@ @THREAD_LIBS@
+LIBS = @SSL_LDFLAGS@ @SSL_LIBS@ @CURL_LDFLAGS@ @CURL_LIBS@ $(top_builddir)/libclamav/libclamav.la $(top_builddir)/libfreshclam/libfreshclam.la @FRESHCLAM_LIBS@ @ZLIB_LIBS@ @THREAD_LIBS@
 
 AM_INSTALLCHECK_STD_OPTIONS_EXEMPT=freshclam$(EXEEXT)
 CLEANFILES=*.gcda *.gcno
diff --git a/libfreshclam/libfreshclam.map b/libfreshclam/libfreshclam.map
index b861f4cda..51841b0b6 100644
--- a/libfreshclam/libfreshclam.map
+++ b/libfreshclam/libfreshclam.map
@@ -28,6 +28,17 @@ FRESHCLAM_PUBLIC {
     mprintf_disabled;
 };
 FRESHCLAM_PRIVATE {
+  global:
+    optparse;
+    optget;
+    optfree;
+    get_version;
+    print_version;
+    check_flevel;
+    drop_privileges;
+    daemonize_parent_wait;
+    daemonize_signal_parent;
+    sendln;
   local:
     *;
 };

-----Original Message-----
From: clamav-users <clamav-users-bounces at lists.clamav.net> On Behalf Of Micah Snyder (micasnyd) via clamav-users
Sent: Thursday, September 3, 2020 9:24 AM
To: ClamAV users ML <clamav-users at lists.clamav.net>
Cc: Micah Snyder (micasnyd) <micasnyd at cisco.com>; Arjen de Korte <build+clamav at de-korte.org>
Subject: Re: [clamav-users] [SUSPECTED SPAM] Re: ClamAV 0.103.0 rc2

Interesting find! Yikes! Ok we'll take a look at it.  

Please keep the feedback coming!

-Micah

-----Original Message-----
From: clamav-users <clamav-users-bounces at lists.clamav.net> On Behalf Of Arjen de Korte via clamav-users
Sent: Thursday, September 3, 2020 1:13 AM
To: ClamAV users ML <clamav-users at lists.clamav.net>
Cc: Arjen de Korte <build+clamav at de-korte.org>
Subject: [SUSPECTED SPAM] Re: [clamav-users] ClamAV 0.103.0 rc2

Citeren Arjen de Korte via clamav-users <clamav-users at lists.clamav.net>:

> I seem to have missed the announcement of clamav-0.103.0-rc2. The 
> problems I reported earlier with clamav-0.103.0-rc seem to be resolved 
> now. All is well again.

Correction: *almost* all is well again. Freshclam doesn't log anything to syslog after startup anymore (updates for instance). So unless I missed updating a setting, this is broken.

     LogSyslog yes
     LogFacility LOG_MAIL

This setting used to work as expected up to and including 0.102.4


_______________________________________________

clamav-users mailing list
clamav-users at lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

_______________________________________________

clamav-users mailing list
clamav-users at lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml