diff options
| author | Lars Wirzenius <liw@liw.fi> | 2020-10-20 10:07:49 +0300 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2020-10-20 10:07:49 +0300 |
| commit | 2f2fe59e2e7733e6b08f93cf57d104e5b570b4c8 (patch) | |
| tree | 932e84aa84f17c931783730269800d5ff07ed677 /contractor.md | |
| parent | 18478cc0d45cc4da97398e3a4e8792c822fb09b1 (diff) | |
| download | ick-contractor-2f2fe59e2e7733e6b08f93cf57d104e5b570b4c8.tar.gz | |
doc: add note that it's possible to guard against risks
Don't want to be too alarmist.
Diffstat (limited to 'contractor.md')
| -rw-r--r-- | contractor.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contractor.md b/contractor.md index 3b4d256..32ba336 100644 --- a/contractor.md +++ b/contractor.md @@ -16,7 +16,7 @@ fundamentally the same. The process is roughly as follows: When the software is run, even if only a small unit of it, it can do anything that the person running the build can do. For example, it can -do any and all of the following: +do any and all of the following, unless guarded against: * delete files * modify files |