What's new in multiSum 1.4.1
Dec 15, 2019
- Added: Some filtering/sorting options to the verification mode. Not entirely satisfied with how these are passed, so this may change.
New in multiSum 1.4 (Dec 9, 2019)
- Added: Two new STDIN input modes, see above for descriptions of -i:2 and -i:3
- Changed: Memory efficient handling of very large verification files.
- Changed: found moderately better whirlpool implementation from splittydev (performance on my machine is now ~46 MB/s vs the old code's 12MB/s)
- Added: New hash family: tiger.
- Added: CNG versions of the MD and SHA hash famlies. These versions invoke direct calls to microsoft's bcrypt.dll to do the math. On many platforms this will use hardware acceleration and give a much faster result.
- Added: New checksum, Fletcher32, like adler but better.
New in multiSum 1.3.1 (Dec 9, 2019)
- Changed: improved ADLER32 performance; should be faster than CRC32 in all cases now.
- Fixed: stupid bug in new shorthand formats.
New in multiSum 1.3 (Dec 9, 2019)
- Added: new hashes: ADLER32, MD2, MD4, RIPEMD160, WHIRLPOOL, BLAKE2B160, BLAKE2B256. Be aware MD2 and WHIRLPOOL are glacially slow; I am looking for optimized implementions of them, or I may just remove them in the next version.
- Added: verification mode, see info on the -v: flag above.
- Added: more shorthand formats: %.sha1%, %.sha256%, %.blake2b%
- Fixed: .net built-in hashes would fail to initilize on some rare platform configurations.
New in multiSum 1.2 (Dec 9, 2019)
- Added: %RELATIVEPATH% as an avalible replacement string.
- Fixed: some fixes in the %.md5% and %.sfv% replacements.
New in multiSum 1.1 (Dec 9, 2019)
- Added: support for accepting files and folders on STDIN. See the -i flag in the usage notes above.
- Added: support for BLAKE2B (only the 512 bit output version). Their c# codebase left a bit to be desired (started with 8 classes, ended up with 2), but I got there in the end. I'm using their fully-unrolled code for the core math; it bumps our executable size up by about 10K, but damn if it dosn't leave the SHAs in the dust.
- Added: better support for long paths, support for hashing NTFS alternate data streams (specify an ADS like so: "file.txt:someOtherStream"). Relative paths are still limited to 260 chars. If in doubt, Prepend \? to long absolute paths.
- Added: %nullAlgo%, a dummy hash that just returns 0 in all cases. For testing IO speed.
- Changed: now targeting .net framework version to 4.6.2 to help with long path support.