-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cases] Opt in for file hashing. #171162
[Cases] Opt in for file hashing. #171162
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Let's ask the InfoSec team (@daniel-gallagher @kayapuskarov @philrose66) if the hash algorithms make sense for them.
Added sha1 too after discussing the PR with @daniel-gallagher |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @adcoelho |
Fixes #171071
Summary
In this PR we opt in for
md5
,sha1
, andsha256
hashes that will be computed and stored automatically on.upload()
calls to the files API.At the moment we don't do anything else with the hashes but we can confirm they are being generate in the Files Tab in the Cases Detail View. The Files Client list API now returns hashes.
See here.