For new Docker-generated repositories, use "auto" hash-policy as default: They might be synced with "sha1"-type repositories, this would render those repositories useless.
check-in: 9a6256cf user: jan.nijtmans tags: trunk

For new Docker-generated repositories, use "auto" hash-policy as default: They might be synced with "sha1"-type repositories, this would render those repositories useless.
Closed-Leaf
check-in: aa92dc8e user: jan.nijtmans tags: mistake

broken.
<h2>Support For SHA3-256</h2>
Prior to Fossil version 2.0 ([/timeline?c=version-2.0|2017-03-03]),
all artifacts in all Fossil repositories were named
by only a SHA1 hash.
Version 2.0 expanded the Fossil file format to allow artifacts to
be named by either SHA1 or SHA3-256 hashes.
(SHA3-256 is the only variant of SHA3 that
Fossil uses for artifact naming, so for the remainder of this article
it will be called simply "SHA3". Similarly, "Hardened SHA1" will
shortened to "SHA1" in the sequel.)
Other than permitting the use of SHA3 in addition to SHA1, there
were no file format changes in Fossil version 2.0 relative

|
|

62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

broken.
<h2>Support For SHA3-256</h2>
Prior to Fossil version 2.0 ([/timeline?c=version-2.0|2017-03-03]),
all artifacts in all Fossil repositories were named
by only a SHA1 hash.
Version 2.0 extended the [./fileformat.wiki|Fossil file format]to allow artifacts to be named by either SHA1 or SHA3-256 hashes.
(SHA3-256 is the only variant of SHA3 that
Fossil uses for artifact naming, so for the remainder of this article
it will be called simply "SHA3". Similarly, "Hardened SHA1" will
shortened to "SHA1" in the sequel.)
Other than permitting the use of SHA3 in addition to SHA1, there
were no file format changes in Fossil version 2.0 relative

This page was generated in about
0.005s by
Fossil 2.8 [7b0dbe8079] 2019-02-20 22:28:24