mirror of
https://github.com/restic/restic.git
synced 2026-01-18 12:54:00 -05:00
9c1d49e312
Removing data based on a policy when the attacker had the opportunity to add data to your repository comes with some considerations. This is added to the 060_forget.rst documentation. That document is also updated to reflect that restic now considers the current system time while running "forget". References to the security considerations section are added: - In `restic forget --help` - In the threat model (design.rst) - In the (030) setup section where an append-only setup is referenced A reference is also to be added to the `rest-server` readme's append-only paragraph (see my fork). This commit also resolves a typo (amount->number for countable noun), changes a password length recommendation into the metric that actually matters when creating passwords (entropy) since I was editing these doc files anyway, and updates the outdated copyright year in `conf.py`. Some wording in 060_forget (line 21..22) was changed to clarify what "forget" and "prune" do, to try and avoid the apparent misconception that "forget" does not remove any data. |
||
|---|---|---|
| .. | ||
| _static | ||
| images/aws_s3 | ||
| logo | ||
| man | ||
| .gitignore | ||
| 010_introduction.rst | ||
| 020_installation.rst | ||
| 030_preparing_a_new_repo.rst | ||
| 040_backup.rst | ||
| 045_working_with_repos.rst | ||
| 050_restore.rst | ||
| 060_forget.rst | ||
| 070_encryption.rst | ||
| 075_scripting.rst | ||
| 080_examples.rst | ||
| 090_participating.rst | ||
| 100_references.rst | ||
| 110_talks.rst | ||
| bash-completion.sh | ||
| cache.rst | ||
| conf.py | ||
| design.rst | ||
| developer_information.rst | ||
| faq.rst | ||
| fish-completion.fish | ||
| index.rst | ||
| Makefile | ||
| manual_rest.rst | ||
| requirements.txt | ||
| REST_backend.rst | ||
| test_irreducibility.gap | ||
| zsh-completion.zsh | ||