-
Notifications
You must be signed in to change notification settings - Fork 30
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
NTFS Stream will not be checked if "checksum in filename" #179
Comments
If a checksum is found in the filename it currently always skips looking into the stream. I could look in both locations. In your case you can remove the underscore as hash delimiter in settings. |
I have already done that. ^^ Checksums are used for integrity checks. Therefore, I think the status "OK" should only apply if all checksums which are found are valid at the same time, otherwise the integrity is violated and there should at least be a warning that there were partial problems. |
I need to use a better language: An example: If it is a matter of dealing with |
If the detection of "Checksum in Filename" recognises something, as in the case of
_20220806_
in the filename (the date of an image in the format of a CRC32), the NTFS stream with the BLAKE3 checksum is no longer checked. That's unexpected when CRC32 calculation is disabled and only BLAKE3-checksum-calculation is enabled.The text was updated successfully, but these errors were encountered: