![]() ![]() Maybe the data could be parsed in the order that gets selected in the ui or specified as arguments in cli, that way the user would be responsible whether the checksum for the "correct" data is calculated or something different. I understand that the result in that case is dependent on the order of the data, but do you think it would be possible to provide that functionality anyway? Then maybe the description in the 7zip interface is a bit misleading, I would still expect "SHA1 checksum for data" to mean "the checksum over the entire selected/specified data". Ah, so its literally all checksums accumulated?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |