Optimization #7353
closedfiles: remove deprecated force-md5 config option
Description
in util-file.c
Updated by Victor Julien about 1 year ago
- Subject changed from Remove deprecated force-md5 config option to files: remove deprecated force-md5 config option
- Target version changed from 8.0.0-beta1 to TBD
This is something we'd only do if we remove md5 tracking, matching and logging.
Updated by Jason Ish about 1 year ago
I'm curious what is the reason to deprecate md5? Besides not being cryptographically secure, it still seems to be in wide use for identifying files.
Updated by Philippe Antoine about 1 year ago
SCLogWarning("deprecated 'force-md5' option "
"found. Please use 'force-hash: [md5]' instead");
Updated by Philippe Antoine about 1 year ago
Victor Julien wrote in #note-1:
This is something we'd only do if we remove md5 tracking, matching and logging.
No, we do md5 tracking, matching and logging with force-hash: [md5] instead of force-md5 in suricata.yaml
Do not we want to have this for 8 ?
Updated by Philippe Antoine about 1 year ago
git grep deprecated shows other stuff like legacy.uricontent ...
Updated by Jason Ish about 1 year ago
Philippe Antoine wrote in #note-4:
Victor Julien wrote in #note-1:
This is something we'd only do if we remove md5 tracking, matching and logging.
No, we do md5 tracking, matching and logging with
force-hash: [md5]instead offorce-md5in suricata.yamlDo not we want to have this for 8 ?
I think this makes sense then. The ticket didn't have enough context to reason about it properly.
Updated by Philippe Antoine about 1 year ago
- Target version changed from TBD to 8.0.0-beta1
Updated by Victor Julien 12 months ago
- Target version changed from 8.0.0-beta1 to 8.0.0-rc1
Updated by Philippe Antoine 10 months ago
- Status changed from New to In Review
- Assignee changed from OISF Dev to Philippe Antoine
Updated by Philippe Antoine 10 months ago
- Status changed from In Review to Closed