Fossil SCM
Clarify that a legitimate reason for removing data is receiving a legitimate legal request, as per https://fossil-scm.org/forum/forumpost/bbfb0e910e. Add the exception for non-versioned data (ie "fossil scrub"). This may need to be explained better.
Commit
1001d86743c256b96ec52513545db4affec4a31388911fa478d40d3e50cb2bc1
Parent
278a2b7453a759b…
1 file changed
+17
+17
| --- www/shunning.wiki | ||
| +++ www/shunning.wiki | ||
| @@ -19,10 +19,17 @@ | ||
| 19 | 19 | copyright was accidentally committed and needs to be backed out. |
| 20 | 20 | |
| 21 | 21 | * A malformed control artifact was inserted and is disrupting the |
| 22 | 22 | operation of Fossil. |
| 23 | 23 | |
| 24 | + * A legitimate legal request was received requiring content to | |
| 25 | + be removed. This would most likely be related to the accidental | |
| 26 | + intellectual property error or spam cases listed above. Some countries | |
| 27 | + recognise software patents, and so allow legal claims targetting code | |
| 28 | + commits. Some countries can require publicly-available encryption | |
| 29 | + software to be taken down if it is committed to the DAG without | |
| 30 | + the correct government authorisation. | |
| 24 | 31 | |
| 25 | 32 | <h2>Alternatives</h2> |
| 26 | 33 | |
| 27 | 34 | All of these are rare cases: Fossil is [./antibot.wiki | designed to |
| 28 | 35 | foil spammers up front], legally problematic check-ins should range from |
| @@ -81,10 +88,20 @@ | ||
| 81 | 88 | repository. Again, nothing is actually deleted; you're just adding |
| 82 | 89 | more information to the repository which corrects a prior |
| 83 | 90 | check-in.</p></li> |
| 84 | 91 | </ul> |
| 85 | 92 | |
| 93 | +<h2>Exception: Non-versioned Content</h2> | |
| 94 | + | |
| 95 | +It is normal and expected to delete data which is not versioned, such as | |
| 96 | +usernames and passwords in the user table. The [/help/scrub|fossil scrub] | |
| 97 | +command will remove all sensitive non-versioned data from a respository. | |
| 98 | + | |
| 99 | +The scrub command will remove user 'bertina', along with their password, | |
| 100 | +any supplied IP address, any concealed email address etc. However, in the | |
| 101 | +DAG, commits by 'bertina' will continue to be visible unchanged even though | |
| 102 | +there is no longer any such user in Fossil. | |
| 86 | 103 | |
| 87 | 104 | <h2>Shunning</h2> |
| 88 | 105 | |
| 89 | 106 | Fossil provides a mechanism called "shunning" for removing content from |
| 90 | 107 | a repository. |
| 91 | 108 |
| --- www/shunning.wiki | |
| +++ www/shunning.wiki | |
| @@ -19,10 +19,17 @@ | |
| 19 | copyright was accidentally committed and needs to be backed out. |
| 20 | |
| 21 | * A malformed control artifact was inserted and is disrupting the |
| 22 | operation of Fossil. |
| 23 | |
| 24 | |
| 25 | <h2>Alternatives</h2> |
| 26 | |
| 27 | All of these are rare cases: Fossil is [./antibot.wiki | designed to |
| 28 | foil spammers up front], legally problematic check-ins should range from |
| @@ -81,10 +88,20 @@ | |
| 81 | repository. Again, nothing is actually deleted; you're just adding |
| 82 | more information to the repository which corrects a prior |
| 83 | check-in.</p></li> |
| 84 | </ul> |
| 85 | |
| 86 | |
| 87 | <h2>Shunning</h2> |
| 88 | |
| 89 | Fossil provides a mechanism called "shunning" for removing content from |
| 90 | a repository. |
| 91 |
| --- www/shunning.wiki | |
| +++ www/shunning.wiki | |
| @@ -19,10 +19,17 @@ | |
| 19 | copyright was accidentally committed and needs to be backed out. |
| 20 | |
| 21 | * A malformed control artifact was inserted and is disrupting the |
| 22 | operation of Fossil. |
| 23 | |
| 24 | * A legitimate legal request was received requiring content to |
| 25 | be removed. This would most likely be related to the accidental |
| 26 | intellectual property error or spam cases listed above. Some countries |
| 27 | recognise software patents, and so allow legal claims targetting code |
| 28 | commits. Some countries can require publicly-available encryption |
| 29 | software to be taken down if it is committed to the DAG without |
| 30 | the correct government authorisation. |
| 31 | |
| 32 | <h2>Alternatives</h2> |
| 33 | |
| 34 | All of these are rare cases: Fossil is [./antibot.wiki | designed to |
| 35 | foil spammers up front], legally problematic check-ins should range from |
| @@ -81,10 +88,20 @@ | |
| 88 | repository. Again, nothing is actually deleted; you're just adding |
| 89 | more information to the repository which corrects a prior |
| 90 | check-in.</p></li> |
| 91 | </ul> |
| 92 | |
| 93 | <h2>Exception: Non-versioned Content</h2> |
| 94 | |
| 95 | It is normal and expected to delete data which is not versioned, such as |
| 96 | usernames and passwords in the user table. The [/help/scrub|fossil scrub] |
| 97 | command will remove all sensitive non-versioned data from a respository. |
| 98 | |
| 99 | The scrub command will remove user 'bertina', along with their password, |
| 100 | any supplied IP address, any concealed email address etc. However, in the |
| 101 | DAG, commits by 'bertina' will continue to be visible unchanged even though |
| 102 | there is no longer any such user in Fossil. |
| 103 | |
| 104 | <h2>Shunning</h2> |
| 105 | |
| 106 | Fossil provides a mechanism called "shunning" for removing content from |
| 107 | a repository. |
| 108 |