Fossil SCM
More tweaks to the hashpolicy.wiki document.
Commit
f5e02af3ab16ec191ac12723f6b050cc5c0f7bd16f45841f86e8b591041f8540
Parent
2f5bb4f04deb9ad…
1 file changed
+5
-5
+5
-5
| --- www/hashpolicy.wiki | ||
| +++ www/hashpolicy.wiki | ||
| @@ -8,15 +8,15 @@ | ||
| 8 | 8 | against SHA1 when it was announced in early 2017. If you are concerned |
| 9 | 9 | about this and its implications for Fossil, simply |
| 10 | 10 | [./quickstart.wiki#install|upgrade to Fossil 2.1 or later], and the |
| 11 | 11 | problem will go away. Everything will continue to work as before. |
| 12 | 12 | |
| 13 | - * All of your legacy repositories will continue to work, without | |
| 14 | - needing any changes or upgrades. | |
| 15 | - * All of your historical check-ins will still have the same historical | |
| 13 | + * Legacy repositories will continue working just as | |
| 14 | + they always have, without any conversions or upgrades. | |
| 15 | + * Historical check-ins will keep their same historical | |
| 16 | 16 | SHA1 names. |
| 17 | - * Your new check-ins will get more secure SHA3-256 hash names. | |
| 17 | + * New check-ins will get more secure SHA3-256 hash names. | |
| 18 | 18 | * Your workflow will be unchanged. |
| 19 | 19 | * Everything will continue as if nothing happened. |
| 20 | 20 | |
| 21 | 21 | But if you are curious and want a deeper understanding of what is |
| 22 | 22 | going on, read on... |
| @@ -188,13 +188,13 @@ | ||
| 188 | 188 | Fossil 2.10 changed the default hash policy to "sha3" mode. So if you |
| 189 | 189 | upgrade to the latest version of Fossil, all of your new artifacts will |
| 190 | 190 | use a SHA3 hash. Legacy SHA1 artifacts continue to use their original |
| 191 | 191 | names but new artifacts will use SHA3 names. |
| 192 | 192 | |
| 193 | -We decided to make the change pur SHA3 since the last known distributor | |
| 193 | +We decided to make the change pure SHA3 since the last known distributor | |
| 194 | 194 | of Fossil 1.x binaries — Debian 9 — was finally replaced in June 2019 |
| 195 | 195 | by a newer version distributing Fossil 2.x. All other known sources of |
| 196 | 196 | Fossil 1.x binaries upgraded well before that point. |
| 197 | 197 | |
| 198 | 198 | Because Fossil 2.x tends to silently upgrade existing repos to SHA-3 |
| 199 | 199 | mode unless carefully forced not to, you probably won't even notice the |
| 200 | 200 | change. |
| 201 | 201 |
| --- www/hashpolicy.wiki | |
| +++ www/hashpolicy.wiki | |
| @@ -8,15 +8,15 @@ | |
| 8 | against SHA1 when it was announced in early 2017. If you are concerned |
| 9 | about this and its implications for Fossil, simply |
| 10 | [./quickstart.wiki#install|upgrade to Fossil 2.1 or later], and the |
| 11 | problem will go away. Everything will continue to work as before. |
| 12 | |
| 13 | * All of your legacy repositories will continue to work, without |
| 14 | needing any changes or upgrades. |
| 15 | * All of your historical check-ins will still have the same historical |
| 16 | SHA1 names. |
| 17 | * Your new check-ins will get more secure SHA3-256 hash names. |
| 18 | * Your workflow will be unchanged. |
| 19 | * Everything will continue as if nothing happened. |
| 20 | |
| 21 | But if you are curious and want a deeper understanding of what is |
| 22 | going on, read on... |
| @@ -188,13 +188,13 @@ | |
| 188 | Fossil 2.10 changed the default hash policy to "sha3" mode. So if you |
| 189 | upgrade to the latest version of Fossil, all of your new artifacts will |
| 190 | use a SHA3 hash. Legacy SHA1 artifacts continue to use their original |
| 191 | names but new artifacts will use SHA3 names. |
| 192 | |
| 193 | We decided to make the change pur SHA3 since the last known distributor |
| 194 | of Fossil 1.x binaries — Debian 9 — was finally replaced in June 2019 |
| 195 | by a newer version distributing Fossil 2.x. All other known sources of |
| 196 | Fossil 1.x binaries upgraded well before that point. |
| 197 | |
| 198 | Because Fossil 2.x tends to silently upgrade existing repos to SHA-3 |
| 199 | mode unless carefully forced not to, you probably won't even notice the |
| 200 | change. |
| 201 |
| --- www/hashpolicy.wiki | |
| +++ www/hashpolicy.wiki | |
| @@ -8,15 +8,15 @@ | |
| 8 | against SHA1 when it was announced in early 2017. If you are concerned |
| 9 | about this and its implications for Fossil, simply |
| 10 | [./quickstart.wiki#install|upgrade to Fossil 2.1 or later], and the |
| 11 | problem will go away. Everything will continue to work as before. |
| 12 | |
| 13 | * Legacy repositories will continue working just as |
| 14 | they always have, without any conversions or upgrades. |
| 15 | * Historical check-ins will keep their same historical |
| 16 | SHA1 names. |
| 17 | * New check-ins will get more secure SHA3-256 hash names. |
| 18 | * Your workflow will be unchanged. |
| 19 | * Everything will continue as if nothing happened. |
| 20 | |
| 21 | But if you are curious and want a deeper understanding of what is |
| 22 | going on, read on... |
| @@ -188,13 +188,13 @@ | |
| 188 | Fossil 2.10 changed the default hash policy to "sha3" mode. So if you |
| 189 | upgrade to the latest version of Fossil, all of your new artifacts will |
| 190 | use a SHA3 hash. Legacy SHA1 artifacts continue to use their original |
| 191 | names but new artifacts will use SHA3 names. |
| 192 | |
| 193 | We decided to make the change pure SHA3 since the last known distributor |
| 194 | of Fossil 1.x binaries — Debian 9 — was finally replaced in June 2019 |
| 195 | by a newer version distributing Fossil 2.x. All other known sources of |
| 196 | Fossil 1.x binaries upgraded well before that point. |
| 197 | |
| 198 | Because Fossil 2.x tends to silently upgrade existing repos to SHA-3 |
| 199 | mode unless carefully forced not to, you probably won't even notice the |
| 200 | change. |
| 201 |