diff options
| author | Kevin Yin <ad8e@users.noreply.github.com> | 2023-11-27 09:12:26 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-27 18:12:26 +0100 |
| commit | bcc8f74b56683f781b19d4d12702a286e428f602 (patch) | |
| tree | d7fc527187be444c0d263d9c173adc21d48bdc03 | |
| parent | 70eed5e9fc7e11816ed00e7c2a087cd06ea08121 (diff) | |
Remove period that could be interpreted as part of the command (#7946)
CVE upgrade steps: remove period that could be interpreted as part of the command
| -rw-r--r-- | docs/changes.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/changes.rst b/docs/changes.rst index f797a9da6..55c241404 100644 --- a/docs/changes.rst +++ b/docs/changes.rst @@ -44,13 +44,14 @@ no matter what encryption mode they use, including "none"): - ``borg check`` would complain about archives without a valid archive TAM. - ``borg check --repair`` would remove such archives! -2. Run ``BORG_WORKAROUNDS=ignore_invalid_archive_tam borg info --debug <repo> 2>&1 | grep TAM | grep -i manifest``. +2. Run: ``BORG_WORKAROUNDS=ignore_invalid_archive_tam borg info --debug <repo> 2>&1 | grep TAM | grep -i manifest`` a) If you get "TAM-verified manifest", continue with 3. b) If you get "Manifest TAM not found and not required", run ``borg upgrade --tam --force <repository>`` *on every client*. -3. Run ``BORG_WORKAROUNDS=ignore_invalid_archive_tam borg list --consider-checkpoints --format='{name} {time} tam:{tam}{NL}' <repo>``. +3. Run: ``BORG_WORKAROUNDS=ignore_invalid_archive_tam borg list --consider-checkpoints --format='{name} {time} tam:{tam}{NL}' <repo>`` + "tam:verified" means that the archive has a valid TAM authentication. "tam:none" is expected as output for archives created by borg <1.0.9. "tam:none" is also expected for archives resulting from a borg rename |