-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combo Filter of Hash Alert leaving some Carved by Led out of list #2266
Comments
Hi @patrickdalla, yes, the reason you described is correct and this behavior is intentional. Users can also search for |
Hi @patrickdalla and @lfcnassif! |
the current database already have some false positives. In fact, in the specific case, all led carved, including the not alerted ones, were true positives, while there were false positives for some not carved zero filled files. any way you decide. |
That is a valid point. I see two options:
@patrickdalla, which solution do you have in mind? |
1 |
Well, I would prefer option 2 over 1, and actually almost suggested it. IMHO that hash filter originally intended to flag files which full hash was found into the hash database tagged as child abuse. Creating another predefined filter for LED carved files is another option. Anyway, as I said, @wladimirleite can take the decision here. |
The filter Hash\ Alert\ (Child\ Porn) in top left combo filters list, lists some CarveLed* files, but not all of them.
Maybe this happens because not the entire file was carved, as LED carving is based only on first bytes, what leads to a different total file hash.
Any way, this inclomplete files could be listed as well. I almost skiped them.
The text was updated successfully, but these errors were encountered: