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
Is your feature request related to a problem? Please describe.
It is my understanding that currently data in the vault is not being checked on checksum variability. Within the vault, the data should not be able to be changed anymore (only metadata). If the checksum of vault data is changing (being variable), it would mean the integrity of that data is lost / changed and action would be required (in its simplest form for example due to bitrot). Such things are especially required for vault data that stay there for at least a decade or more.
Describe the solution you'd like
It would be good to have general automated checks that flag data which have checksums changed so that data integrity can be restored.
Describe alternatives you've considered
Doing it all ourselves for each individual instance. But this could become troublesome if every instance does this themselves.
The text was updated successfully, but these errors were encountered:
Danny-dK
changed the title
[FEATURE] Automated flagging of vault data when checksum changed over time
[FEATURE] Automated evaluation of checksums over time of data in the vault.
Feb 27, 2024
Is your feature request related to a problem? Please describe.
It is my understanding that currently data in the vault is not being checked on checksum variability. Within the vault, the data should not be able to be changed anymore (only metadata). If the checksum of vault data is changing (being variable), it would mean the integrity of that data is lost / changed and action would be required (in its simplest form for example due to bitrot). Such things are especially required for vault data that stay there for at least a decade or more.
Describe the solution you'd like
It would be good to have general automated checks that flag data which have checksums changed so that data integrity can be restored.
Describe alternatives you've considered
Doing it all ourselves for each individual instance. But this could become troublesome if every instance does this themselves.
The text was updated successfully, but these errors were encountered: