Thanks for your response. Let comment per algorithm:
Both would be nice to have, but they both share the same "problem". That is that they have a dynamic iteration count. Therefore comparison of benchmarks always lead to invalid results.
Yes I agree somewhat. But which version exactly? And what about the old guaranteed cracking modes of office?
Both are raw hashes and unlikely to be used as password storage hash. A more valid example for "long time to come" would be Argon 2, but we don't support that one.
Doesn't sound economic
Quote:Maybe VeraCrypt (in addition to TrueCrypt or as replacement for TrueCrypt) would make sense.
...
PBKDF2 (because it's probably used in a number of different places?)
Both would be nice to have, but they both share the same "problem". That is that they have a dynamic iteration count. Therefore comparison of benchmarks always lead to invalid results.
Quote:I think also some MS office modes could make sense within the reduced list, because it's also used a lot by hashcat users.
Yes I agree somewhat. But which version exactly? And what about the old guaranteed cracking modes of office?
Quote:SHA-3 or SHA-512 (or an algorithm likely to be used for a long time to come, to compare benchmarks over time)
Both are raw hashes and unlikely to be used as password storage hash. A more valid example for "long time to come" would be Argon 2, but we don't support that one.
Quote:For selecting groups of hashes for focused benchmarking, it might be useful to select all of the ones in a particular family:
Doesn't sound economic