On Feb 25, 2019, at 10:44, G.W. Haywood via clamav-users
wrote:
>
> Hi there,
>
> On Mon, 25 Feb 2019, Al Varnell wrote:
>
>> ... the strings you provided appear to contain an extra digit. I
>> thought hex strings always contain an even number of digits?
>
> Just as decimal strings are string
Hi there,
On Mon, 25 Feb 2019, Al Varnell wrote:
... the strings you provided appear to contain an extra digit. I
thought hex strings always contain an even number of digits?
Just as decimal strings are strings composed of decimal digits and can
be any length, hexadecimal strings are strings
Our setup:
1) have freshclam download via Internet on a Solaris 10 x86 server in DMZ
2) an ex-colleague who left us served out cvd/cld via httpd on this Solaris
server
3) have internal RHEL7 freshclam try to update from that Solaris httpd
server using the private mirror
In the internal RHEL7's, /e
Hello,
We have been using ClamAV for several months, and are noticing some strange
behaviour when scanning files (and archives) above a certain size.
The documentation states:
--max-filesize=#n can be anything up to 4GB
--max-scansize=#n can be anything up to 4GB
We are however experiencing dif
I just took a peek at the code to try to answer your question. I'm not sure
why, exactly, but yes there is an explicit MAX_LDB_SUBSIGS set to 64.
Regards,
-Micah
> On Feb 24, 2019, at 9:35 PM, Al Varnell via clamav-users
> wrote:
>
> I can’t comment on whether or not there is a 65 field limit
