On Sep 12, 2015, at 2:26 AM, Stephan Beal <[email protected]> wrote: > > On Sat, Sep 12, 2015 at 12:57 AM, Warren Young <[email protected]> wrote: > For instance, why even mention “SHA1 Hash” on the checkin details page in > fossil ui, from src/info.c? Why not something more generic, like “checkin > ID”? > > The checkin ID is the hash of the manifest for the checkin.
Yes, I know that. The question is not, “Why is the checkin ID a SHA-1 hash?” The question is, “Why does this UI web page have to *say* that it is a SHA-1 hash?” If this page just said “checkin ID,” what would be lost? What would be gained is that people wouldn’t be trying to work out how to match sha1sum commands to Fossil output, and Fossil would be free to switch to a different algorithm later if that seemed like a good idea. And indeed, maybe it is a good idea, since SHA-1 is nearing its EOL for cryptographic use: https://www.google.com/?q=sha-1%20end%20of%20life _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
