2
2
mirror of https://github.com/octoleo/restic.git synced 2024-10-31 19:02:32 +00:00

Merge pull request #3482 from MichaelEischer/changelog-3429

Add changelog for #3246 and #3429
This commit is contained in:
Alexander Neumann 2021-09-08 09:15:40 +02:00 committed by GitHub
commit bf9c8771a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 29 additions and 0 deletions

View File

@ -0,0 +1,17 @@
Enhancement: Add upload checksum for azure, gs, s3 and swift backends
Up to now only the B2 backend and partially the Swift backend verified the
integrity of uploaded (encrypted) files. The verification works by informing
the backend about the expected hash of the uploaded file. This allows the
backend to verify the upload and thereby rules out any data corruption during
upload.
We have added upload checksums for the azure, gs, s3 and swift backends.
Restic can now be used to store backups in S3 buckets which have Object Lock
enabled.
https://github.com/restic/restic/issues/2202
https://github.com/restic/restic/issues/2700
https://github.com/restic/restic/issues/3023
https://github.com/restic/restic/pull/3246

View File

@ -0,0 +1,12 @@
Enhancement: Verify that new or modified keys were stored correctly
When adding a new key or changing the password of a key, restic just created the
new key (and removed the old one, when changing the password). There was no
verification that the new key was stored correctly and that it work. As the
repository cannot be decrypted without a valid key file, this could in rare
cases cause the repository to become inaccessible.
We have added a check that the new key actually works before continuing. This
can protect against some (rare) cases of hardware or storage problems.
https://github.com/restic/restic/pull/3429