[Bro-Dev] [JIRA] (BIT-1257) Same file id generated for potentially different files

[Seth Hall (JIRA)]

    [ https://bro-tracker.atlassian.net/browse/BIT-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18218#comment-18218 ] 

Seth Hall commented on BIT-1257:
--------------------------------

Ah!  I think it's perfectly reasonable to make our default behavior a bit closer to RFC2616.  I'll take a look into it soon.

At the very least, if someone does want the more liberal file combining they can add it back with a separate script (which I'll probably include with Bro somewhere).  I'll take this ticket to make sure I deal with this soon.

> Same file id generated for potentially different files
> ------------------------------------------------------
>
>                 Key: BIT-1257
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1257
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: Bro
>    Affects Versions: git/master, 2.3
>         Environment: CentOS 6
>            Reporter: Jimmy Jones
>         Attachments: fa.bro, sample-samefileid.pcap
>
>
> Attached sample contains two HTTP downloads of the same URL from the same client, but there are no guarantees that the files is actually the same (no Etags etc - in this case it actually is the same, but lets pretend they were different...). However the file analysis framework seems to give the same file ID in file_name and file_chunk for both downloads.
> Think this is something to do with Range requests as doesn't happen if do "normal" HTTP requests.



--
This message was sent by Atlassian JIRA
(v6.4-OD-05-009#64003)