Fossil SCM

Updated the "A Pure SHA3 Future" section of www/hashpolicy.wiki to track the recent decision to make "sha3" mode the default in Fossil 2.10.

wyoung 2019-08-07 00:53 trunk
Commit c6e8558f2706e763ccffbaa55903264567fa8058acb4411d6d08871c0f9e2033
1 file changed +9 -16
--- www/hashpolicy.wiki
+++ www/hashpolicy.wiki
@@ -168,21 +168,14 @@
168168
artifacts with SHA3 names, because once you do that your recalcitrant
169169
coworkers will no longer be able to collaborate.
170170
171171
<h2>A Pure SHA3 Future</h2>
172172
173
-At some point in the future, after everybody has finally upgraded to
174
-Fossil 2.0 or later, the default hash policy will probably change to
175
-"sha3", or maybe even "shun-sha1". By the time that happens, you will
176
-probably already be using SHA3 on all your projects and so you are
177
-unlikely to notice.
178
-
179
-This probably won't happen until after all of the operating systems
180
-shipping binary versions of Fossil switch to Fossil 2.1 or later. The
181
-big standout is Debian Stretch (v9), since it still ships Fossil 1.37
182
-due to its stable packages policy. Stretch will be the current release
183
-version of Debian until "some time mid 2019" according to
184
-[https://lists.debian.org/debian-devel-announce/2018/04/msg00006.html|the latest
185
-published release plan]. Debian Stretch will then remain in
186
-support until June 2022. We do not yet know if we will switch the
187
-default hash policy during that window or not until after Stretch is
188
-fully out of support.
173
+Fossil 2.10 will change the default hash policy to "sha3" mode. We
174
+decided to make the change since the last known distributor of Fossil
175
+1.x binaries — Debian 9 — was finally replaced in June 2019 by a newer
176
+version distributing Fossil 2.x. All other known sources of Fossil 1.x
177
+binaries upgraded well before that point.
178
+
179
+Because Fossil 2.x tends to silently upgrade existing repos to SHA-3
180
+mode unless carefully forced not to, you probably won't even notice the
181
+change.
189182
--- www/hashpolicy.wiki
+++ www/hashpolicy.wiki
@@ -168,21 +168,14 @@
168 artifacts with SHA3 names, because once you do that your recalcitrant
169 coworkers will no longer be able to collaborate.
170
171 <h2>A Pure SHA3 Future</h2>
172
173 At some point in the future, after everybody has finally upgraded to
174 Fossil 2.0 or later, the default hash policy will probably change to
175 "sha3", or maybe even "shun-sha1". By the time that happens, you will
176 probably already be using SHA3 on all your projects and so you are
177 unlikely to notice.
178
179 This probably won't happen until after all of the operating systems
180 shipping binary versions of Fossil switch to Fossil 2.1 or later. The
181 big standout is Debian Stretch (v9), since it still ships Fossil 1.37
182 due to its stable packages policy. Stretch will be the current release
183 version of Debian until "some time mid 2019" according to
184 [https://lists.debian.org/debian-devel-announce/2018/04/msg00006.html|the latest
185 published release plan]. Debian Stretch will then remain in
186 support until June 2022. We do not yet know if we will switch the
187 default hash policy during that window or not until after Stretch is
188 fully out of support.
189
--- www/hashpolicy.wiki
+++ www/hashpolicy.wiki
@@ -168,21 +168,14 @@
168 artifacts with SHA3 names, because once you do that your recalcitrant
169 coworkers will no longer be able to collaborate.
170
171 <h2>A Pure SHA3 Future</h2>
172
173 Fossil 2.10 will change the default hash policy to "sha3" mode. We
174 decided to make the change since the last known distributor of Fossil
175 1.x binaries — Debian 9 — was finally replaced in June 2019 by a newer
176 version distributing Fossil 2.x. All other known sources of Fossil 1.x
177 binaries upgraded well before that point.
178
179 Because Fossil 2.x tends to silently upgrade existing repos to SHA-3
180 mode unless carefully forced not to, you probably won't even notice the
181 change.
 
 
 
 
 
 
 
182

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button