Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Updated the Debian Stretch speculation bit at the end of the hashpolicy document with latest results from the forum thread. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
9d673f04f5a9ce41b563b3fa365e937c |
| User & Date: | wyoung 2019-01-09 12:31:05 |
Context
|
2019-01-10
| ||
| 06:03 | Fixed an errant use of a Markdown hyperlink in a Fossil wiki document. check-in: 15cbb09d user: wyoung tags: trunk | |
|
2019-01-09
| ||
| 12:31 | Updated the Debian Stretch speculation bit at the end of the hashpolicy document with latest results from the forum thread. check-in: 9d673f04 user: wyoung tags: trunk | |
|
2019-01-08
| ||
| 19:08 | Restore the ability to delete a wiki page. check-in: e947378e user: drh tags: trunk | |
Changes
Changes to www/hashpolicy.wiki.
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 |
Of course, if some members of your team stubbornly refuse to upgrade past Fossil 1.37, you should avoid changing the hash policy and creating artifacts with SHA3 names, because once you do that your recalcitrant coworkers will no longer be able to collaborate. <h2>A Pure SHA3 Future</h2> At some point in the future, years from now, after everybody has finally upgraded to Fossil 2.0 or later, the default hash policy will probably change to "sha3", or maybe even "shun-sha1". By the time that happens, you will probably already be using SHA3 on all your projects and so you are unlikely to notice. This probably won't happen until after all of the operating systems shipping binary versions of Fossil switch to Fossil 2.1 or later. The big standout is Debian Stretch (9.0), which is not expected to be replaced until March 2019, and it won't fall out of support until June 2022. We do not yet know if we will switch the default hash policy during that window or not until after Debian 9 is fully out of support. |
| | | | | | | > > | | > > > > |
165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 |
Of course, if some members of your team stubbornly refuse to upgrade past Fossil 1.37, you should avoid changing the hash policy and creating artifacts with SHA3 names, because once you do that your recalcitrant coworkers will no longer be able to collaborate. <h2>A Pure SHA3 Future</h2> At some point in the future, after everybody has finally upgraded to Fossil 2.0 or later, the default hash policy will probably change to "sha3", or maybe even "shun-sha1". By the time that happens, you will probably already be using SHA3 on all your projects and so you are unlikely to notice. This probably won't happen until after all of the operating systems shipping binary versions of Fossil switch to Fossil 2.1 or later. The big standout is Debian Stretch (v9), since it still ships Fossil 1.37 due to its stable packages policy. Stretch will be the current release version of Debian until "some time mid 2019" according to [the latest published release plan][deb10]. Debian Stretch will then remain in support until June 2022. We do not yet know if we will switch the default hash policy during that window or not until after Stretch is fully out of support. [deb10]: https://lists.debian.org/debian-devel-announce/2018/04/msg00006.html |