[clamav-users] PrivateMirror vs HTTPproxy

2018-07-09 Thread Paul Kosinski
For several years now, we've been using HTTPproxy to reduce the load on the public ClamAV servers. We don't use Squid or anything general purpose like that, but rather a simple-minded ClamAV-only server that listens on a private port, only supports the HTTP that freshclam actually uses to get the

Re: [clamav-users] max file size & system damage

2018-07-09 Thread Paul Kosinski
A Linux process that exhausts physical memory may cause problems, depending on how the kernel is configured. Look up "linux oom" with your favorite search engine. On Mon, 9 Jul 2018 21:59:46 + "Rovan, Jim (IMS)" wrote: > Hello, everyone. > > I understand how I can increase the max file

[clamav-users] max file size & system damage

2018-07-09 Thread Rovan, Jim (IMS)
Hello, everyone. I understand how I can increase the max file size for command line or clamd scanning. But I also see many references to possible severe system damage that could occur by scanning large files. The clamd.conf file explicitly warns against setting several limits too high. I have

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

2018-07-09 Thread Paul Kosinski
I have changed the way we use freshclam to mitigate the sync problem with the new Cloudflare mirror regime -- which, by the way, *still* seems to lag what the DNS TXT record reports. What I have done is to introduce a pretesting phase before invoking freshclam. Our new update method operates in

[clamav-users] Trouble compiling - Re: ClamAV 0.100.1 has been released!

2018-07-09 Thread Kevin A. McGrail
On 7/9/2018 12:55 PM, Joel Esler (jesler) wrote: > https://blog.clamav.net/2018/07/clamav-01001-has-been-released.html   Hi All, Compiling is throwing an error in freshclam for me. make[2]: Entering directory `/usr/src/clamav-0.100.1/freshclam'   CC   output.o   CC   optparser.o   CC 

[clamav-users] ClamAV 0.100.1 has been released!

2018-07-09 Thread Joel Esler (jesler)
https://blog.clamav.net/2018/07/clamav-01001-has-been-released.html ClamAV 0.100.1 is a hotfix release to patch a set of vulnerabilities. • Fixes for the following CVE's: • CVE-2017-16932: Vulnerability in libxml2 dependency (affects ClamAV on Windows only).

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Tilman Schmidt
According to the manpage, the default value of --bytecode-timeout is sixty seconds. Shouldn't that be ample for scanning a 6 MB file on a current processor? But I'll keep in mind to retry with a higher value should the problem reappear. Thanks, Tilman Am 09.07.2018 um 16:22 schrieb Micah Snyder

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Micah Snyder (micasnyd)
It's a pretty common error if you lower the --bytecode-timeout value. By contrast, you can also raise --bytecode-timeout higher than the default until the errors go away if you want to scan those files, and don't wish to delete the one triggering the timeout. It isn't entirely surprising that

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Tilman Schmidt
Am 09.07.2018 um 11:45 schrieb Pavel Kosina: > No, its not working this way. -i prints out infected files. These files > (bytecode jit error) are probably  considered as not infected. That's why I said "drop the -i option". "Drop" means "remove", "omit", "erase", "do not use". Just change

Re: [clamav-users] CompressLocalDatabase does not work

2018-07-09 Thread Al Varnell
Updates are provided as daily.cdiff files which are integrated into the daily database after the daily.cvd file is decompressed into a daily.cld. -Al- On Mon, Jul 09, 2018 at 03:03 AM, Kretschmer, Jens wrote: > after a couple of days the daily.cvd file is replaced by daily.cld. Why does > this

[clamav-users] CompressLocalDatabase does not work

2018-07-09 Thread Kretschmer, Jens
Hi, I'm trying to setup a private mirror at our site. I plan to download the signatures on a server using freshclam and then provide the signatures with an apache web server for the clients. On the server I set "CompressLocalDatabase yes" in /etc/freshclam.conf to reduce the filesize of the

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Matus UHLAR - fantomas
Am 09.07.2018 um 10:37 schrieb pee...@email.cz: Is it possile to let print out with the error messages what file is it? Tilman Schmidt napsal(a) dne 9.7.2018 v 10:58: If you drop the -i option it will print each file as it scans it. On 09.07.18 11:45, Pavel Kosina wrote: No, its not

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Pavel Kosina
No, its not working this way. -i prints out infected files. These files (bytecode jit error) are probably considered as not infected. Tilman Schmidt napsal(a) dne 9.7.2018 v 10:58: If you drop the -i option it will print each file as it scans it. Am 09.07.2018 um 10:37 schrieb

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Tilman Schmidt
If you drop the -i option it will print each file as it scans it. Am 09.07.2018 um 10:37 schrieb pee...@email.cz: > I see. > > Is it possile to let print out with the error messages what file is it? > As you can see, I excluded all movies and so on >

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Tilman Schmidt
Would have gladly done so, had anyone hinted at that possibility. Now it's too late, the file is gone. Am 09.07.2018 um 10:37 schrieb Al Varnell: > Agree that apparently nobody knows, but a lot of us care. > > I only wish you had submitted that file to the ClamAV signature team as > I suspect

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Al Varnell
Agree that apparently nobody knows, but a lot of us care. I only wish you had submitted that file to the ClamAV signature team as I suspect they would have figured it out by now. -Al- ClamXAV User On Mon, Jul 09, 2018 at 01:27 AM, Tilman Schmidt wrote: > I've been trying in vain to get an

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread peekaa
I see. Is it possile to let print out with the error messages what file is it? As you can see, I excluded all movies and so on (mp4|MP4|mkv|MKV|avi|AVI|wmv|WMV|ts|TS|flv|FLV|mov|MOV|JPG|jpg|mp3|MP3|tc) that are very big, that may cause this, but I might forget something other big too.

Re: [clamav-users] Bytecode 86 failed to run

2018-07-09 Thread Tilman Schmidt
I've been trying in vain to get an answer on that one since 2018-06-20. For me it's bytecode 73, otherwise the same. Looks like no-one knows or cares. I ended up bisecting the scan and removing the file whose scan triggered the message. Luckily it wasn't needed for the operation of the affected