Richard Hipp wrote: [...] > I think the above doesn't really work for an application like Fossil. I > think that a prefix of the SHA1 hash should encode to a prefix of the > mnemonic, and the other way arround too - a prefix of the mnemonic > should decode back to a prefix of the original hash. [...] > The hex hash is encoded into mnemonic words in 4-byte or 8-character > chunks. > > HHH -> WORD -> HH > HHHHHH -> WORD-WORD -> HHHHH > HHHHHHHH -> WORD-WORD-WORD -> HHHHHHHH
Yes, that makes a lot of sense for Fossil's particular use case (which the mnemonic encoding algorithm wasn't designed for, of course). I'll have a go tonight and see what happens --- the encoder/decoder is wrong and needs to be rewritten anyway. -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "USER'S MANUAL VERSION 1.0: The information presented in this │ publication has been carefully for reliability." --- anonymous │ computer hardware manual
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
