Re: [clamav-users] Input Stream Scanning for very large files

2019-02-06 Thread Dennis Peterson
Should have been file type as reported by the file command. Any usage of ClamAV outside its design objectives is vulnerable to failure, but the method I pointed out works, period. But if asked if I thought it was worth it I would say no, of course not. The OP seems determined though. ClamAV is

Re: [clamav-users] Input Stream Scanning for very large files

2019-02-03 Thread Ángel
On 2019-01-25 at 18:43 -0800, Dennis Peterson wrote: > You can easily use the unix split command and cat to scan files of any size. > Or > use perl to break stream file segments to the stream. The first file in a > split > or segment contains the file time and will need to be concatenated to

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-29 Thread Tilman Schmidt
Am 28.01.19 um 18:02 schrieb G.W. Haywood: > On Sat, 26 Jan 2019, Dennis Peterson wrote: > On 1/25/19 11:38 AM, G.W. Haywood wrote: > >> > ... I'd call it madness. >> >> Sometimes it is a management or compliance requirement. > > Are these not just synonyms? Not quite, though often quite close.

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-28 Thread G.W. Haywood
Hi there, On Sat, 26 Jan 2019, Dennis Peterson wrote: On 1/25/19 11:38 AM, G.W. Haywood wrote: > ... I'd call it madness. Sometimes it is a management or compliance requirement. Are these not just synonyms? -- 73, Ged. ___ clamav-users mailing

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Dennis Peterson
Sometimes it is a management or compliance requirement. dp On 1/25/19 11:38 AM, G.W. Haywood wrote: Hi there, On Fri, 25 Jan 2019, Kushal Kumar wrote: Re: Input Stream Scanning for very large files ... how do you propose I should scan an archive of 100GB ( let's say) size. I wouldn't

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Dennis Peterson
You can easily use the unix split command and cat to scan files of any size. Or use perl to break stream file segments to the stream. The first file in a split or segment contains the file time and will need to be concatenated to the beginning of each split or segment so clamav knows what it

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Paul Kosinski
"If you think there's a problem, why not deal with it before it gets into your archives?" Because maybe somebody else created the archive; and I believe there have been cases where the archive itself exploited a flaw in the code used to expand the archive. On Fri, 25 Jan 2019 19:38:27 +

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Micah Snyder (micasnyd)
By no means am I happy with the 2-4GB file size limit, but it will take a fair amount of work to properly change all of the integer types throughout the codebase to handle larger file offsets. The specific task of raising the limit for 64bit machines isn't on our roadmap, but is definitely

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread G.W. Haywood
Hi there, On Fri, 25 Jan 2019, Kushal Kumar wrote: Re: Input Stream Scanning for very large files ... how do you propose I should scan an archive of 100GB ( let's say) size. I wouldn't propose anything like that, because I'd call it madness. If you think there's a problem, why not deal

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Paul Kosinski
I understand that it's impractical for ClamAV to scan exceedingly large files, as it could fill up RAM and/or page forever. But the current 4GB hard limit is overly restrictive, especially since 32-bit addresses and numbers are ancient history in current OSes. In particular, scanning big archives

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-25 Thread Micah Snyder (micasnyd)
Regarding specific limits, I'm sorry to say that ClamAV is presently limited to max file size of 4GB on most systems (and, I think unintentionally, 2GB on some systems). -Micah On Jan 24, 2019, at 4:23 PM, J.R. mailto:themadbea...@gmail.com>> wrote: I think I framed my problem statement

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-24 Thread J.R.
> I think I framed my problem statement differently. > So, our requirement is similar the one asked by John in the > below link. I do not know if the solution proposed is a correct one.. > Also, how do you propose I should scan an archive of 100GB ( let's say) size. > Does clamav have any

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-24 Thread Kushal Kumar
Hi Micah, Thanks for the information. ! I think I framed my problem statement differently. So, our requirement is similar the one asked by John in the below link. I do not know if the solution proposed is a correct one.. Also, how do you propose I should scan an archive of 100GB ( let's say)

Re: [clamav-users] Input Stream Scanning for very large files

2019-01-24 Thread Micah Snyder (micasnyd)
Unfortunately, ClamAV is not designed to parse and scan chunks of files individually. ClamAV does file typing by pattern matching starting from the beginning of a file. Without this information, ClamAV won't know what type of file it is scanning and will treat it as generic binary or text