This bug was fixed in the package clamav - 0.96.3+dfsg-1ubuntu2
---
clamav (0.96.3+dfsg-1ubuntu2) maverick; urgency=low
* debian/usr.bin.freshclam: updated to give read access to
@{PROC}/[0-9]*/status and @{PROC}/filesystems. The latter is covered by
the base abstraction, bu
** Changed in: clamav (Ubuntu)
Status: Confirmed => Fix Committed
--
apparmor blocks freshclam process info after latest update
https://bugs.launchpad.net/bugs/645061
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
apparmor blocks freshclam process info after latest update
https://bugs.launchpad.net/bugs/645061
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
[09/22-194642]owner @{PROC}/[0-9]*/status r,
[09/22-195205] cemc: /proc/filesystems r, is fine
Added these two lines to /etc/apparmor.d/usr.bin.freshclam and
/etc/apparmor.d/usr.sbin.clamd , and after reloading apparmor and
restarting clamav-freshclam and clamav-daemon the log entries no lon
According to upstream, this is for selinux and pax detection. This
permission problem doesn't affect anything, except for apparmor logs
since we have neither and they wouldn't co-exist with apparmor if a user
had switched to them.
The detection process opens /proc/pid/status and if it can't be op
** Changed in: clamav (Ubuntu)
Importance: Undecided => Low
** Changed in: clamav (Ubuntu)
Status: New => Confirmed
--
apparmor blocks freshclam process info after latest update
https://bugs.launchpad.net/bugs/645061
You received this bug notification because you are a member of Ubuntu
Confirmed on Lucid with (not yet) backported clamav 0.96.3 from clamav-
ppa.
Seems like this is some new feature in 0.96.3 where freshclam (and
indeed clamav-daemon too) does some checking in /proc/self and also
/proc/filesystems. Attached some syslog entries which appear exactly
after freshclam i
Updater seemed to work fine:
Received signal: wake up
ClamAV update process started at Wed Sep 22 05:00:55 2010
main.cld is up to date (version: 52, sigs: 704727, f-level: 44, builder: sven)
Downloading daily-11996.cdiff [100%]
daily.cld updated (version: 11996, sigs: 130710, f-level: 53, builder:
Hi
Does this affect freshclam in any way, is it not working, does it give
any other errors besides this log entry?
--
apparmor blocks freshclam process info after latest update
https://bugs.launchpad.net/bugs/645061
You received this bug notification because you are a member of Ubuntu
Server Tea
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/645061/+attachment/1621864/+files/Dependencies.txt
--
apparmor blocks freshclam process info after latest update
https://bugs.launchpad.net/bugs/645061
You received this bug notification because you are a member of
10 matches
Mail list logo