ok, it seems that limits.maxfilesize limits to 10MB, but I am able to
scan up to 25MB files. see below:
(when I scan 30MB file the data scanned is 0, Why is like that? and I
am able to scan nearly 25MB)
Every byte in sample file is 'B8'
ls -l
total 60656
-rw-r--r-- 1 root root 1600 Dec 17
On 2008-12-17 18:37, Thomasz Blaszczyk wrote:
ok, it seems that limits.maxfilesize limits to 10MB, but I am able to
scan up to 25MB files. see below:
(when I scan 30MB file the data scanned is 0, Why is like that? and I
am able to scan nearly 25MB)
Read the archives of -users. This
On 2008-12-17 20:27, Thomasz Blaszczyk wrote:
I just got first results here,
http://omploader.org/vMTExNA
What do you think about them?
What kind of data was scanned?
Was it hand-crafted, automatically generated, or real world files?
What is the confidence of the values you measured?
(I
What kind of data was scanned?
Was it hand-crafted, automatically generated, or real world files?
I create files by calling in loop function: fputc('my_byte')
i.e:
file_builder -n sizeoffile -xB8
So entire file consists of bytes 'B8' and I create 2MB, 4MB file, up
to 60MB files
What is the
On 2008-12-17 21:28, Thomasz Blaszczyk wrote:
What kind of data was scanned?
Was it hand-crafted, automatically generated, or real world files?
I create files by calling in loop function: fputc('my_byte')
i.e:
file_builder -n sizeoffile -xB8
So entire file consists of bytes 'B8'
You might want to scan something resembling a real world file, and I'm
not saying to use /dev/urandom instead of B8.
I can think of a much more efficient algorithm to match on B8 bytes...
Ohh, yes, there will be several test cases, B8 bytes is only one
There will be also test case upon DNA
On 2008-12-17 18:12, Thomasz Blaszczyk wrote:
Hi,
I have notice kind of limitation in ClamAV. When time of scanning one
file is longer than 1 sec, the entire file scan is droped.
There is no such limitation in ClamAV.
Best regards,
--Edwin
___