Skip to content
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

Compute integrity for must-gather dumps #1847

Open
tnozicka opened this issue Mar 19, 2024 · 0 comments · May be fixed by #1848
Open

Compute integrity for must-gather dumps #1847

tnozicka opened this issue Mar 19, 2024 · 0 comments · May be fixed by #1848
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@tnozicka
Copy link
Member

We should add integrity information to must-gather dump to help us identify when it was tempered with. Removing some sensitive files can be justified but in my experience it is greatly misused but most importantly never reported as such, so we end up wondering whether the dumps are not present because they were removed, or because the collection didn't work properly.

@tnozicka tnozicka added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 19, 2024
@tnozicka tnozicka self-assigned this Mar 19, 2024
@tnozicka tnozicka linked a pull request Mar 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant