Re:Multihash – self-describing hashes
by LeoPanthera on Sunday February 26, 2017 @05:05PM
(#13740242)
For a few extra bytes you could have the ASCII name of the hash function. "sha256" is pretty clear, for example.
And then your code would still need a table mapping the string to the implementation.
Yes, but that's just one table - for implementations that are supported by code. I don't need the table to just understand what this hash is - only to verify it. And, if I want to add my private hash, I don't need to update shared tables and be worried some other hash would have the same ID as mine. I can just use reasonably unique string.
It still needs a table, but it doesn't need consensus on what those names mean.
If someone says "sha2", that doesn't mean bcrypt, after all!
Re:Multihash – self-describing hashes
by LeoPanthera on Sunday February 26, 2017 @06:29PM
(#13740658)
But at least you could work out the mapping in your head, without having to refer to a numeric table.
Re:Multihash – self-describing hashes
by _prometheus on Sunday February 26, 2017 @05:33PM
(#13740407)
yep, exactly :)
Won't some kind of table always be necessary unless the type contains actual bytecode implementing the hash algorithm?