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

Power-User-Problem: It's unclear which checksums are checked. #180

Open
Thunderbolt32 opened this issue Oct 12, 2022 · 0 comments
Open

Power-User-Problem: It's unclear which checksums are checked. #180

Thunderbolt32 opened this issue Oct 12, 2022 · 0 comments

Comments

@Thunderbolt32
Copy link

Everything (all checksum and storage methods) can be calculated and saved in one go, but not checked, because in practice, RapidCRC Unicode seems to prefer CRC32 in the filename over CRC32 in the NTFS stream (for example) - if both are used and there is a missmatch between them -, but that's not reported to the user. Now it has somehow become intransparent which checksums RapidCRC-Unicode recognizes and are actually checked against. I don't know, if a list with the checked checksumtypes like "Filename-CRC32, Checksumfile-SHA1, NTFS-BLAKE3" in a new table-column would make it more transparent or if it will introduce much complexity without a real benifit.

The problem only occurs when several checksums are used at the same time.: I think it only affects a few power-users and the benefit might not justify the effort. I use RapidCRC Unicode intensively myself, but it is not a real problem for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant