4 ms·
There's no need to identify the hash algorithm unless multiple versions are used in the same context, which is rarely the case and often defeats the purpose of
by jmiserez 6y ago
There's no need to identify the hash algorithm unless multiple versions are used in the same context, which is rarely the case and often defeats the purpose of using a hash in the first place.
- michaelt 6y agoLoads of things have multiple hash options - from /etc/shadow supporting 6 different password hashes, to Maven storing foo.jar alongside foo.jar.md5 and foo.jar.sha1 and apt-get providing both an MD5sum and a SHA256 in the package index, to TLS and SSH and GPG supporting multiple algorithms for compatibility. None of them do it with "sha1://" though...