On Sun, Feb 26, 2017 at 9:43 PM, Richard Hipp <d...@sqlite.org> wrote:
> (2) Artifacts can be identified via multiple hash algorithms. The > initial implementation will support SHA1 and SHA3-228. (For brevity, > SHA3-228 will hereafter be referred to as K228.) > (3) The low-level file formats > (https://www.fossil-scm.org/fossil/doc/trunk/www/fileformat.wiki) are > unchanged except that the artifact hashes are allowed to be longer > than 40 hex digits for alternative hash algorithms. For K228, the > hashes are 56 hex digits long. Other hash algorithms may be supported > in future releases as long as each hash algorithm has a unique hash > length, thus enabling Fossil to figure out which algorithm is being > used simply by looking at the length of the hash. > How about a '!' (ASCII 33d) card which tells Fossil which hash is in use for a given artifact? '!' sorts before all other cards, placing it first in the manifest. Maybe even add the artifact type, e.g.: ! m k228 Where m=manifest, though there's probably little reason to abbreviate it: ! manifest SHA3-228 (Pardon my brevity - _still_ on medical leave and can't be as active online as i'd like.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
