Bug 1227506

Summary: freshclam is not quiet anymore
Product: [openSUSE] openSUSE Tumbleweed Reporter: Björn Voigt <bjoernv>
Component: SecurityAssignee: Reinhard Max <max>
Status: CONFIRMED --- QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: Andreas.Stieger, meissner
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Björn Voigt 2024-07-08 11:30:21 UTC 
Since the latest snapshots (tested on TW 20240704) freshclam ignores the "--quiet" option. This is annoying if freshclam is handled via cronjob.

# freshclam 
ClamAV update process started at Mon Jul  8 13:28:05 2024
daily.cld database is up-to-date (version: 27330, sigs: 2064003, f-level: 90, builder: raynman)
main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
bytecode.cld database is up-to-date (version: 335, sigs: 86, f-level: 90, builder: raynman)
# freshclam --quiet
ClamAV update process started at Mon Jul  8 13:28:09 2024
daily.cld database is up-to-date (version: 27330, sigs: 2064003, f-level: 90, builder: raynman)
main.cld database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
bytecode.cld database is up-to-date (version: 335, sigs: 86, f-level: 90, builder: raynman)
# rpm -q libfreshclam3 clamav
libfreshclam3-1.3.1-1.1.x86_64
clamav-1.3.1-1.1.x86_64
Comment 2 Reinhard Max 2024-07-08 12:56:58 UTC 
Yes, the overhaul of the logging facility was done incompletely.
logg() should not be called directly anymore, but cli_warnmsg, cli_errmsg, etc. instead. They call logg() thhrough msg_callback(), which in turn calls libclamav_msg_callback() or libclamav_msg_callback_quiet() depending on the --quiet switch, with the latter callback doing the filtering, if in place.
Comment 3 Reinhard Max 2024-07-08 13:43:28 UTC 
Reported upstream:
https://github.com/Cisco-Talos/clamav/issues/1302