[Bro] File extraction after checking hash.
philosnef at gmail.com
Tue Oct 4 07:33:12 PDT 2016
Hm, good point. Is there somewhere in the analysis framework where you can
say, if a file is above x bytes, kill the analysis process? I ask, because
I see this as somewhat related to the gridftp problem at lbl. If we have
large tarballs or zip files or whatever crossing the wire, killing those
off at say, a 5 gig point or so, seems reasonable. As you mentioned that is
quite a lot of memory being consumed by extraction. :/
On Tue, Oct 4, 2016 at 10:21 AM, Seth Hall <seth at icir.org> wrote:
> > On Oct 4, 2016, at 8:47 AM, erik clark <philosnef at gmail.com> wrote:
> > Can't you simply write a script that calls file extract at a later date?
> I would think to hook it into file intel which runs after the file analysis
> (its comparing hashes) and extract at that point, not before...
> I've been thinking about some potential directions we could go that might
> open the door to doing this in some cases for the next release, but for now
> imagine that your file is 10G. We can't keep that much data in memory but
> you don't know the file hash until you've seen every byte of that file.
> You can't choose to extract the file at the end because all of the content
> for that file is already gone. You'd have to extract it up front and make
> the decision to keep it or delete it after the fact.
> Seth Hall
> International Computer Science Institute
> (Bro) because everyone has a network
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bro