<commit_before>This file describes changes relevant to all users that are made in each
released version of restic from the perspective of the user.

Important Changes in 0.X.Y
==========================


Small changes
-------------

 * We've added code to detect old cache directories of repositories that
   haven't been used in a long time, restic now prints a note when it detects
   that such dirs exist. Also, the option `--cleanup-cache` was added to
   automatically remove such directories. That's not a problem because the
   cache will be rebuild once a repo is accessed again.
   https://github.com/restic/restic/pull/1436

 * The cache directory on Windows and Darwin was not correct, instead the
   directory `.cache` was used.
   https://github.com/restic/restic/pull/1454

 * By default, the access time for files and dirs is not saved any more. It is
   not possible to reliably disable updating the access time during a backup,
   so for the next backup the access time is different again. This means a lot
   of metadata is saved. If you want to save the access time anyway, pass
   `--with-atime` to the `backup` command.
   https://github.com/restic/restic/pull/1452

Important Changes in 0.8.0
==========================

 * A vulnerability was found in the restic restorer, which allowed attackers in
   special circumstances to restore files to a location outside of the target
   directory. Due to the circumstances we estimate this to be a low-risk
   vulnerability, but urge all users to upgrade to the latest version of restic.

   Exploiting the vulnerability requires a Linux/Unix system which saves
   backups via restic and a Windows systems which restores files from the repo.
   In addition, the attackers need to be able to create create files with
   arbitrary names which are then saved to the restic repo. For example, by
   creating a file named "..\test.txt" (which is a perfectly legal filename on
   Linux) and restoring a snapshot containing this file on Windows, it would be
   written to the parent of the target directory.

   We'd like to thank <NAME> for reporting this responsibly!

   https://github.com/restic/restic/pull/1445

 * The s3 backend used the subdir `restic` within a bucket if no explicit path
   after the bucket name was specified. Since this version, restic does not use
   this default path any more. If you created a repo on s3 in a bucket without
   specifying a path within the bucket, you need to add `/restic` at the end of
   the repository specification to access your repo: `s3:s3.amazonaws.com/bucket/restic`
   https://github.com/restic/restic/issues/1292
   https://github.com/restic/restic/pull/1437

 * We've added a local cache for metadata so that restic doesn't need to load<commit_msg>Add entry to CHANGELOG<commit_after>This file describes changes relevant to all users that are made in each
released version of restic from the perspective of the user.

Important Changes in 0.X.Y
==========================


Small changes
-------------

 * We've added code to detect old cache directories of repositories that
   haven't been used in a long time, restic now prints a note when it detects
   that such dirs exist. Also, the option `--cleanup-cache` was added to
   automatically remove such directories. That's not a problem because the
   cache will be rebuild once a repo is accessed again.
   https://github.com/restic/restic/pull/1436

 * The cache directory on Windows and Darwin was not correct, instead the
   directory `.cache` was used.
   https://github.com/restic/restic/pull/1454

 * By default, the access time for files and dirs is not saved any more. It is
   not possible to reliably disable updating the access time during a backup,
   so for the next backup the access time is different again. This means a lot
   of metadata is saved. If you want to save the access time anyway, pass
   `--with-atime` to the `backup` command.
   https://github.com/restic/restic/pull/1452

 * We've improved the s3 backend to work with DigitalOcean Spaces. In addition,
   handling of SIGPIPE was removed.
   https://github.com/restic/restic/pull/1459
   https://github.com/restic/restic/issues/1457

Important Changes in 0.8.0
==========================

 * A vulnerability was found in the restic restorer, which allowed attackers in
   special circumstances to restore files to a location outside of the target
   directory. Due to the circumstances we estimate this to be a low-risk
   vulnerability, but urge all users to upgrade to the latest version of restic.

   Exploiting the vulnerability requires a Linux/Unix system which saves
   backups via restic and a Windows systems which restores files from the repo.
   In addition, the attackers need to be able to create create files with
   arbitrary names which are then saved to the restic repo. For example, by
   creating a file named "..\test.txt" (which is a perfectly legal filename on
   Linux) and restoring a snapshot containing this file on Windows, it would be
   written to the parent of the target directory.

   We'd like to thank <NAME> for reporting this responsibly!

   https://github.com/restic/restic/pull/1445

 * The s3 backend used the subdir `restic` within a bucket if no explicit path
   after the bucket name was specified. Since this version, restic does not use
   this default path any more. If you created a repo on s3 in a bucket without
   specifying a path within the bucket, you need to add `/restic` at the end of
   the repository specification to access your repo: `s3:s3.amazonaws.com/bucket/restic`
   https://github.com/restic/restic/issues/1292
   https://github.com/restic/restic/pull/1437

 * We've added a local cache for metadata so that restic doesn't need to load
{'fraction_non_alphanumeric': 0.07378472222222222, 'fraction_numerical': 0.012673611111111111, 'mean_word_length': 3.5831344470962607, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 14, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1912799', 'n_tokens_mistral': 1572, 'n_tokens_neox': 1477, 'n_words': 807}