You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mangusm opened this issue
Jan 24, 2024
· 3 comments
Assignees
Labels
buguse for describing something not working as expectedcriticaluse to identify critical bug to fix ASAPsolveduse to identify issue that has been solved (must be linked to the solving PR)
When creating the entity, all fuzzy hashes are removed here resulting in valuesFiltering being an empty array and an error being thrown here
It looks like this behavior is a result of addressing this issue. It makes sense why it was done, but I have a need to be able to create file observables that I only have a fuzzy hash for.
Stack trace:
UNSUPPORTED_ERROR: Invalid filter configuration
at error (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/config/errors.js:8:10)
at UnsupportedError (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/config/errors.js:77:51)
at buildLocalMustFilter (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/database/engine.js:1650:9)
at buildSubQueryForFilterGroup (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/database/engine.js:1669:37)
at buildSubQueryForFilterGroup (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/database/engine.js:1660:30)
at elQueryBodyBuilder (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/database/engine.js:2097:35)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at elPaginate (/home/mangus/github/opencti/opencti/opencti-platform/opencti-graphql/src/database/engine.js:2464:16)
Screenshots (optional)
The text was updated successfully, but these errors were encountered:
mangusm
added
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 24, 2024
nino-filigran
added
feature
use for describing a new feature to develop
and removed
bug
use for describing something not working as expected
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 25, 2024
@mangusm Thanks for your request. We have indeed changed the implementation as you have mentionned .We'll fix this but also consider this request as a feature, since tackling in a quick way will not work easily. For now, the solution that we have identified are:
be able to create an observable with a fuzzy hash
add the hash in the UI (not existing at the moment)
remove the deduplication mechanism for these fuzzy hashes (or maybe just on the the last 6 bits which can be the reason why 2 sames hashes exist for different files).
nino-filigran
added
bug
use for describing something not working as expected
critical
use to identify critical bug to fix ASAP
and removed
feature
use for describing a new feature to develop
labels
Jan 25, 2024
buguse for describing something not working as expectedcriticaluse to identify critical bug to fix ASAPsolveduse to identify issue that has been solved (must be linked to the solving PR)
Description
Attempting to create a File observable with only fuzzy hashes results in an error
Environment
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
A File observable with an SSDEEP hash
Actual Output
Additional information
When creating the entity, all fuzzy hashes are removed here resulting in
valuesFiltering
being an empty array and an error being thrown hereIt looks like this behavior is a result of addressing this issue. It makes sense why it was done, but I have a need to be able to create file observables that I only have a fuzzy hash for.
Stack trace:
Screenshots (optional)
The text was updated successfully, but these errors were encountered: