Autogenerated freshclam.conf should not mention now-deprecated option SafeBrowsing

Bug #1926324 reported by Nils Toedtmann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clamav (Ubuntu)
Fix Released
Low
Sergio Durigan Junior

Bug Description

The post install routine of clamav-freshclam generates /etc/clamav/freshclam.conf that contains the option "SafeBrowsing" (either using the default "false", or "true", depending on user input)

But that option is deprecated, and since 0.103.2+dfsg-0ubuntu0.18.04.1 "freshclam --quite" issues a noisy message

  "WARNING: Ignoring deprecated option SafeBrowsing at /etc/clamav/freshclam.conf:22"

The PostInst should generate a default freshclam.conf without "SafeBrowsing". And, on update, the "SafeBrowsing" should be removed from an untouched pre-existing default freshclam.conf.

description: updated
description: updated
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Thanks for taking the time to report a bug and help making Ubuntu better.

I can obviously confirm this problem, but it's a low priority one (upstream seems to have decided that the SafeBrowsing option simply doesn't do anything anymore, so it's not "dangerous" to leave it in the configuration file). For this reason, I think it's better to address this on Debian's clamav package.

I went ahead and filed the following MR against Debian clamav:

https://salsa.debian.org/clamav-team/clamav/-/merge_requests/3

Eventually this will be accepted (I hope), and then Ubuntu's clamav will incorporate the fix once it's merged. Feel free to subscribe to the MR above if you'd like to follow its progress.

Thanks.

Changed in clamav (Ubuntu):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Sergio Durigan Junior (sergiodj)
Changed in clamav (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

This has been fixed in version 0.103.2+dfsg-2.

ubuntu:
 clamav | 0.98.1+dfsg-4ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 clamav | 0.99+dfsg-1ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 clamav | 0.99.4+addedllvm-0ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x
 clamav | 0.100.3+dfsg-0ubuntu0.14.04.1 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 clamav | 0.100.3+dfsg-0ubuntu0.14.04.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 clamav | 0.102.2+dfsg-2ubuntu1 | focal | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.2+dfsg-0ubuntu0.16.04.1 | xenial-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 clamav | 0.103.2+dfsg-0ubuntu0.16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 clamav | 0.103.3+dfsg-1 | impish | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-0ubuntu0.18.04.1 | bionic-security | source, amd64, arm64, armhf, i386, ppc64el, s390x
 clamav | 0.103.5+dfsg-0ubuntu0.18.04.1 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x
 clamav | 0.103.5+dfsg-1~20.04.1 | focal-security | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-1~20.04.1 | focal-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-1~21.10.1 | impish-security | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-1~21.10.1 | impish-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-1 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
 clamav | 0.103.5+dfsg-1 | kinetic | source, amd64, arm64, armhf, ppc64el, riscv64, s390x

Changed in clamav (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.