Thus said Richard Hipp on Mon, 27 Feb 2017 21:50:43 -0500: > (9) There are no changes to the file formats, other than relaxing the > size constraint on artifact hashes - allowing hash to be greater than > or equal to 40 characters rather than requiring it to be exactly 40 > characters.
The F-card in a manifest is currently defined as: F filename ?SHA1-hash? ?permissions? ?old-name? So the SHA1-hash will be a variable-length hash >= 40. How will a program (including Fossil) that interprets the F-card know what hash algorithm was used? Or will it not matter? Will it simply have to know that Fossil uses X, Y and Z algorithms and to compute one of each until a match is found (perhaps using length as an indicator)? Also, when choosing a P-card to include in a manifest, how will a choice be made for hash to be included in the P-card? Likewise for the Q-card? > (11) URLs and command-line arguments can use either the display name > or any of the aliases for an artifact. I assume that the same Ambiguous Artifact page that is used when a short UUID is used will also be used when the aliases have similar length collisions? e.g. the SHA1 hash 0005 might have a collision with a 4 character prefix of a different SHA3-256 hash? Regarding: > (12) Web pages that show details about an artifact will be titled by > the display name, but will also show all aliases. What about command line tools? This may seem off-the-wall, but I often use a tty that is a standard 24 rows 80 columns: $ fossil stat repository: /home/amb/development/fossil/fossil.fossil local-root: /home/amb/download/tarballs/fossil/ config-db: /home/amb/.fossil checkout: 5ed8477b6c65b3286a14b92abb9c925d7a63ccf2 2017-02-27 14:46:01 UTC parent: ccdafa2a93e7bcefa1b4d0ea7474f9ce84c690f2 2017-02-26 16:30:44 UTC tags: trunk comment: The smallest SHA3 hash size is 224 bits, not 228 bits. (user: drh) Will the format of this change to allow for larger UUIDs that would otherwise wrap on such a terminal? Thanks, Andy -- TAI64 timestamp: 4000000058b4f77a _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
