I too see these messages on the the console and have found no way of
identifying the files by using any of the clamav flags.
This is what I would do
*sudo /usr/bin/clamscan -r / /tmp/clamav.log 21*
The file */tmp/clamav.libreoffice.log *will contain details of ALL files
irrespective of
Ignore the asterisks in my previous note they just encapsulate the highlighted
parts of the note.
Alex
On Tuesday 04 Mar 2014 09:08:15 mcmurchy1917-cla...@yahoo.co.uk wrote:
I too see these messages on the the console and have found no way of
identifying the files by using any of the clamav
I too reported the false positive. I supplied the offending file was that
correct?
I have 18 other different files that report the same exploit like so -
559 /root$ freshclam
ClamAV update process started at Thu Dec 12 08:54:47 2013
main.cvd is up to date (version: 55, sigs: 2424225, f-level:
Henri
You have helped in some way, the fdpass option did make a difference in
that it allowed clamdscan to return the full filename. Before I was just
getting a file descriptor.
I can not run clamdscan successfully if I
* have the standard user, i.e. not root, as a member of the clamav
Hello Henri
Thanks for the quick response. I tried that and this is what I get if running
from a standard user -
$ clamdscan --fdpass nw1700.p65
ERROR: Can't connect to clamd: Permission denied
--- SCAN SUMMARY ---
Infected files: 0
Total errors: 1
Time: 0.000 sec (0 m 0
Hello Henri
Results below -
ls -la nw1700.p65
-rwxr--r-- 1 alex users 6825472 Oct 24 2012 nw1700.p65*
id
uid=1001(alex) gid=100(users)
groups=100(users),7(lp),12(mail),15(man),17(audio),19(cdrom),20(games),21(slocate),27(mysql),33(sshd),50(ftp),83(plugdev),86(netdev),93(scanner)
Thanks
Hello Maarten
ls -lrt /var/run/clamav/clamd.socket
srw-rw 1 clamav clamav 0 Dec 3 15:32 /var/run/clamav/clamd.socket=
ls -lrt /tmp/clamav-milter.socket
srw-r--r-- 1 clamav root 0 Dec 3 15:32 /tmp/clamav-milter.socket=
Just wondering should a standard user belong to the clamav group. Is
I regularly use clamscan to scan my filesystem using cron. I'm now also looking
to scan individual files from either the command line or from a file manager
like dolphin.
I've tried both clamscan and clamdscan.
clamscan works as from a standard user but takes 21 seconds as it has to load
the
