Try our Chrome extension
Easily add the current web-page from your browser directly into your changedetection.io tool, more great features coming soon!
Chrome Webstore
Changedetection.io needs your support!
You can help us by supporting changedetection.io on these platforms;
- Rate us at AlternativeTo.net
- Star us on GitHub
- Follow us at Twitter/X
- G2 Software reviews
- Check us out on LinkedIn
- And tell your friends and colleagues :)
The more popular changedetection.io is, the more time we can dedicate to adding amazing features!
Many thanks :)
changedetection.io team
Noch nicht vor Sekunden
False
Noch nicht vor Sekunden
Auslösender Text Ignorierter Text Blockierter Text
vor 12 Stunden
Skip to content
Navigation Menu
Sign in Appearance settings
* Platform
+ AI CODE CREATION
o GitHub Copilot Write better code with AI
o GitHub Copilot app Direct agents from issue to merge
o MCP Registry Integrate external tools
+ DEVELOPER WORKFLOWS
o Actions Automate any workflow
o Codespaces Instant dev environments
o Issues Plan and track work
o Code Review Manage code changes
o Code Quality Enforce quality at merge
+ APPLICATION SECURITY
o GitHub Advanced Security Find and fix vulnerabilities
o Code security Secure your code as you build
o Secret protection Stop leaks before they start
+ EXPLORE
o Why GitHub
o Documentation
o Blog
o Changelog
o Marketplace
View all features
* Solutions
+ BY COMPANY SIZE
o Enterprises
o Small and medium teams
o Startups
o Nonprofits
+ BY USE CASE
o App Modernization
o DevSecOps
o DevOps
o CI/CD
o View all use cases
+ BY INDUSTRY
o Healthcare
o Financial services
o Manufacturing
o Government
o View all industries
View all solutions
* Resources
+ EXPLORE BY TOPIC
o AI
o Software Development
o DevOps
o Security
o View all topics
+ EXPLORE BY TYPE
o Customer stories
o Events & webinars
o Ebooks & reports
o Business insights
o GitHub Skills
+ SUPPORT & SERVICES
o Documentation
o Customer support
o Community forum
o Trust center
o Partners
View all resources
* Open Source
+ COMMUNITY
o GitHub Sponsors Fund open source developers
+ PROGRAMS
o Security Lab
o Maintainer Community
o Accelerator
o GitHub Stars
o Archive Program
+ REPOSITORIES
o Topics
o Trending
o Collections
* Enterprise
+ ENTERPRISE SOLUTIONS
o Enterprise platform AI-powered developer platform
+ AVAILABLE ADD-ONS
o GitHub Advanced Security Enterprise-grade security features
o Copilot for Business Enterprise-grade AI features
o Premium Support Enterprise-grade 24/7 support
* Pricing
Type / to search
Sign in
Sign up Appearance settings
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Uh oh!
There was an error while loading. Please reload this page.
restic / restic Public
* Notifications You must be signed in to change notification settings
* Fork 1.8k
* Star 35.5k
* Code
* Issues 460
* Pull requests 99
* Actions
* Projects
* Security and quality 0
* Insights
Additional navigation options
* Code
* Issues
* Pull requests
* Actions
* Projects
* Security and quality
* Insights
Releases: restic/restic
Releases Tags
Releases · restic/restic
Release list
* restic 0.19.1
* restic 0.19.0
* restic 0.18.1
* restic 0.18.0
* restic 0.17.3
* restic 0.17.2
* restic 0.17.1
* restic 0.17.0
* restic 0.16.5
* restic 0.16.4
Previous Next
Jump to release
* restic 0.19.1
* restic 0.19.0
* restic 0.18.1
* restic 0.18.0
* restic 0.17.3
* restic 0.17.2
* restic 0.17.1
* restic 0.17.0
* restic 0.16.5
* restic 0.16.4
Previous Next
restic 0.19.1
restic 0.19.1 Latest
Latest
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 05 Jul 08:13
v0.19.1
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
6aa3a51
Changelog for restic 0.19.1 (2026-07-05)
The following sections list the changes in restic 0.19.1 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #5234: Prevent mounting over the repository directory
* Fix #5667: Skip inaccessible backup source paths
* Fix #5722: Update mount latest symlink after snapshot reload
* Fix #21866: Hide stats progress bar in JSON mode
* Fix #21869: Restore old behavior of snapshots --latest <n> without --group-by
* Fix #21876: Show timezone location in snapshots output
* Fix #21879: Prevent crash in mountpoint validation if mountpoint is inaccessible
* Fix #21895: Remove read-only files via the SFTP backend on Windows servers
* Fix #21899: Make backup respect excludes for duplicate directory entries
Details
* Bugfix #5234: Prevent mounting over the repository directory
Using a local repository directory as the mount target — or a path that contains it, or that it contains — caused the FUSE server to read its own backend files through the new mount, deadlocking the kernel and requiring a long reboot to recover.
Restic now resolves both paths and refuses any such overlap with a clear error before mounting.
#5234 #5348
* Bugfix #5667: Skip inaccessible backup source paths
The backup command only skipped source paths that did not exist. A path that could not be accessed for another reason, such as a malformed path on Windows, was kept and produced an empty snapshot. Restic now skips any such path and aborts if none remain.
#5667 #21852
* Bugfix #5722: Update mount latest symlink after snapshot reload
When restic mount was kept running while new snapshots were created, the new snapshots appeared in the mountpoint, but the latest symlink could still point to the previously latest snapshot. Restic now invalidates the cached snapshot directory entries after a snapshot reload so that latest points to the newest snapshot.
#5722 #21873
* Bugfix #21866: Hide stats progress bar in JSON mode
Since restic 0.19.0, the stats command shows a progress bar. This progress bar was unintentionally displayed also when using the --json option, mixing regular text output with JSON. This is now fixed.
#21866 #21871
* Bugfix #21869: Restore old behavior of snapshots --latest <n> without --group-by
Restic 0.19.0 accidentally changed the behavior of snapshots --latest <n> to no longer group snapshots by host and paths by default.
The snapshots --latest <n> command now again uses the old behavior of grouping by host and paths when --group-by is not specified. However, when specifying --group-by the output is still grouped as requested, as in restic 0.19.0.
#21869 #21875
* Bugfix #21876: Show timezone location in snapshots output
With restic 0.19.0, the snapshots command printed the current timezone when listing snapshots. However, that timezone label might change during the year, for example with daylight saving time. Restic now prints a more consistent and shorter version of the text.
#21876 https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
* Bugfix #21879: Prevent crash in mountpoint validation if mountpoint is inaccessible
Since restic 0.19.0, the mount command validates a mountpoint before loading the repository. If restic was unable to stat the mountpoint, this would result in a crash. This has now been fixed to correctly return an error instead.
#21879
* Bugfix #21895: Remove read-only files via the SFTP backend on Windows servers
Since restic 0.19.0, repository files on the SFTP backend are marked read-only after save. On Windows SFTP servers, removing them failed with a permission error. The SFTP backend now clears the read-only flag before removing the file.
#21895 #21897
* Bugfix #21899: Make backup respect excludes for duplicate directory entries
Since restic 0.19.0, backing up a directory with duplicate directory entries always produced "Warning: at least one source file could not be read", even when those files were excluded. This has now been fixed.
#21899 #21900
Assets 31
* restic-0.19.1.tar.gz
sha256:bb9b1a19040744d26d8a79be029d4e6b189c45ccc9d8831d7fe367d3c33df725
23 MB 2026-07-05T08:13:16Z
* restic-0.19.1.tar.gz.asc
sha256:6e5ad378c9aa9ab25b87e3bbed66e5dbb6eca57d4659f292d97352a69f86c3ff
833 Bytes 2026-07-05T08:13:16Z
* restic_0.19.1_aix_ppc64.bz2
sha256:a8e0fc448966b31c2e5d4e21d75f1f97d9164f43a4bc0a5154554a0ef6a8136c
9.29 MB 2026-07-05T08:13:10Z
* restic_0.19.1_darwin_amd64.bz2
sha256:c38d579622cf602f665234c5a8c315030b6cf70656028fe6dc29a786b60e5f35
10 MB 2026-07-05T08:13:03Z
* restic_0.19.1_darwin_arm64.bz2
sha256:7be0a144ccc377880f294204aa271d76e4b79554b42a751151d425ce6ebac143
9.28 MB 2026-07-05T08:12:57Z
* restic_0.19.1_dragonfly_amd64.bz2
sha256:db5a689c51a04b6e937ab4ca836791465606cf26770ae9106b3a95a98784b4b6
9.49 MB 2026-07-05T08:12:50Z
* restic_0.19.1_freebsd_386.bz2
sha256:92a6d61692f677db915c547466897ad2440c2bc3ce1aa32660be8590b180c427
9.09 MB 2026-07-05T08:12:44Z
* restic_0.19.1_freebsd_amd64.bz2
sha256:579787cac3fc9041bcddc90b2e77128be01d23bfe5233434da8d291aeb024a10
9.58 MB 2026-07-05T08:12:37Z
* restic_0.19.1_freebsd_arm.bz2
sha256:ab7a99840f25015ae346685e13f0e202380a632ffa097c46bc88c876ea0658ee
9.01 MB 2026-07-05T08:12:30Z
* restic_0.19.1_linux_386.bz2
sha256:c715a3de2fffb70a4c7864ef2d195db8bad96bc0284757cd5bd0f43362f2a191
9.11 MB 2026-07-05T08:12:23Z
* Source code (zip)
2026-07-05T07:52:50Z
* Source code (tar.gz)
2026-07-05T07:52:50Z
* Show all 31 assets Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 22 DianaNites, xplosionmind, liv-io, adriankirchner, paulgalow, RomelSan, alexycodes, ame0011, Brah-Timo, oshirinap, and 12 more reacted with thumbs up emoji 😄 1 dmotte reacted with laugh emoji 🎉 9 DianaNites, qappell, maurizio-scalia, reneleonhardt, shd2h, bigjoe54321, dcorto, TwistTheNeil, and dmotte reacted with hooray emoji ❤️ 18 oliverklee, smlx, DianaNites, Safari77, baekis1185, xplosionmind, qappell, 56k-modem, firescry, kinghat, and 8 more reacted with heart emoji 🚀 13 svengreb, smlx, DianaNites, sdellenb, baekis1185, sokai, adrianmusante, simonemargio, dimlev, bigjoe54321, and 3 more reacted with rocket emoji 👀 2 xplosionmind and TwistTheNeil reacted with eyes emoji
All reactions
* 👍 22 reactions
* 😄 1 reaction
* 🎉 9 reactions
* ❤️ 18 reactions
* 🚀 13 reactions
* 👀 2 reactions
42 people reacted
restic 0.19.0
restic 0.19.0
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 09 Jun 17:06
v0.19.0
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
12875cc
Changelog for restic 0.19.0 (2026-06-09)
The following sections list the changes in restic 0.19.0 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #2034: Support serving a restic mount of a Windows system via Samba
* Fix #4447: Use mode 0700 for repository directories created over SFTP
* Fix #4467: Exit with code 3 when some backup source paths do not exist
* Fix #4759: Error out when environment variables hold invalid values
* Fix #5233: Return exit code 3 when failing to remove snapshots
* Fix #5258: Exit with code 130 on SIGINT
* Fix #5280: Reject impossible find time bounds immediately
* Fix #5280: Make find --pack list blobs for tree packs
* Fix #5354: Allow rclone and sftp backends when running in background
* Fix #5427: Correctly restore ACL inheritance state on Windows
* Fix #5477: Password prompt was sometimes not shown for backup -v
* Fix #5487: Mark repository files read-only when using the SFTP backend
* Fix #5586: Correctly handle snapshots --group-by with --latest
* Fix #5595: Avoid spurious chmod errors on certain file backends
* Fix #5683: Prevent backup --stdin-from-command from hanging
* Fix #5757: Respect --user and --host in key passwd
* Fix #21820: Correct handling of duplicate index entries
* Fix #21820: Correctly handle pack files missing from the index
* Chg #5293: Prune small packfiles more aggressively
* Chg #5767: Prevent excluding paths explicitly passed to backup
* Chg #21791: Update dependencies and require Go 1.25 or newer
* Enh #3326: Limit check to snapshots selected by filters
* Enh #3572: Support restoring ownership by name on UNIX systems
* Enh #3738: Optional GitHub token for self-update API requests
* Enh #4278: Support include filters in the rewrite command
* Enh #4728: Support zstd compression levels fastest and better
* Enh #4868: Include repository ID in the filesystem name used by mount
* Enh #5175: Add status counters to copy in verbose text output
* Enh #5352: Support excluding cloud-backed files on macOS
* Enh #5383: Reduce progress bar refresh rates to decrease energy usage
* Enh #5424: Enable Windows filesystem privileges before file access
* Enh #5440: Make --host override environment variable RESTIC_HOST
* Enh #5448: Support configuring nice and ionice in the Docker image
* Enh #5453: Copy multiple snapshots in batches
* Enh #5523: Add Open Container Initiative labels to release Docker image
* Enh #5531: Reduce Azure storage costs by optimizing uploads
* Enh #5562: Rewrite only changed status lines each frame
* Enh #5588: Show timezone context in snapshots output
* Enh #5610: Reduce check, copy, diff and stats memory usage
* Enh #5689: Show more detailed progress for stats
* Enh #5713: Significantly speed up index loading
* Enh #5718: Stricter and earlier validation of the mount point
Details
* Bugfix #2034: Support serving a restic mount of a Windows system via Samba
A repository mounted using restic mount on a POSIX system could not use Samba to serve files from backups of Windows systems, while backups of non-Windows systems could be served successfully. This has now been fixed.
#2034 #4382 #21784
* Bugfix #4447: Use mode 0700 for repository directories created over SFTP
When creating a repository over SFTP, restic created the repository directories with the SFTP server's default permissions, often 0755, rather than the 0700 permissions it uses for local repositories.
Restic now creates these directories with 0700 permissions.
#4447 #21817
* Bugfix #4467: Exit with code 3 when some backup source paths do not exist
Restic used to exit with code 0 when a top-level backup source path was missing, and exited with code 3 only when a child path under an existing source did not exist. Scripts that relied on the exit code could therefore treat an incomplete backup as success.
Restic now exits with code 3 when any backup source path does not exist.
#4467 #5347
* Bugfix #4759: Error out when environment variables hold invalid values
If the environment variables RESTIC_COMPRESSION, RESTIC_PACK_SIZE, or RESTIC_READ_CONCURRENCY could not be parsed, restic used to ignore them. Restic now fails with an error unless the same setting is overridden on the command line.
#4759 #5592 #5700
* Bugfix #5233: Return exit code 3 when failing to remove snapshots
Previously, the forget command returned exit code 0 when it failed to remove one or more snapshots. This was misleading to scripts.
The forget command now instead returns exit code 3 when failing to remove one or more snapshots.
#5233 #5322
* Bugfix #5258: Exit with code 130 on SIGINT
Restic used to return exit code 1 on SIGINT. It now returns 130, the usual convention for a process stopped by Ctrl-C.
#5258 #5363
* Bugfix #5280: Reject impossible find time bounds immediately
The find command now fails with an error when both --oldest and --newest are set and --oldest is later than --newest.
#5280 #5310
* Bugfix #5280: Make find --pack list blobs for tree packs
The find --pack <tree-pack> command now also reports blobs for packs that only contain tree blobs.
#5280 #5664
* Bugfix #5354: Allow rclone and sftp backends when running in background
Previously, starting restic in the background could result in unexpected behavior when using the rclone or sftp backends. For example, restic -r rclone:./example --insecure-no-password init & could cause the calling bash shell to exit unexpectedly.
This has now been fixed.
#5354 #5358 #5493 #5494
* Bugfix #5427: Correctly restore ACL inheritance state on Windows
Since security descriptor backups were added in restic 0.17.0, Access Control Entry inheritance was not restored correctly on Windows; restored permissions were always marked as explicit (not inherited) even when they were inherited from a parent folder.
The inheritance flags are now correctly applied when restoring the security descriptor, preserving the original permission structure.
#5427 #5465
* Bugfix #5477: Password prompt was sometimes not shown for backup -v
The repository password prompt could be hidden when running the backup -v command. This has now been fixed.
#5477 #5554
* Bugfix #5487: Mark repository files read-only when using the SFTP backend
Files created through the SFTP backend previously stayed writable. New files now ...
Read more
Assets 31
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 41 jvandenbroek, Safari77, LeSpocky, mholt, Guti014, BackSpace54, CroniC-, sg-eys, liv-io, nicotsx, and 31 more reacted with thumbs up emoji 😄 3 insertish, nicotsx, and dmotte reacted with laugh emoji 🎉 21 insertish, eTernal1911, qappell, mholt, Guti014, BackSpace54, matt-laird, nicotsx, dmotte, ma-lalonde, and 11 more reacted with hooray emoji ❤️ 17 oliverklee, jedi453, qappell, SigHunter, mikix, nicotsx, dmotte, LuckyFrost, firescry, simonemargio, and 7 more reacted with heart emoji 🚀 9 dmotte, derhuerst, svengreb, overdarki, kapsiR, sokai, santiagobiali, roschaefer, and bigjoe54321 reacted with rocket emoji 👀 2 CrazyVito11 and xplosionmind reacted with eyes emoji
All reactions
* 👍 41 reactions
* 😄 3 reactions
* 🎉 21 reactions
* ❤️ 17 reactions
* 🚀 9 reactions
* 👀 2 reactions
73 people reacted
restic 0.18.1
restic 0.18.1
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 21 Sep 18:24
v0.18.1
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
7d0aa7f
Changelog for restic 0.18.1 (2025-09-21)
The following sections list the changes in restic 0.18.1 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #5324: Correctly handle backup --stdin-filename with directory paths
* Fix #5325: Accept RESTIC_HOST environment variable in forget command
* Fix #5342: Ignore "chmod not supported" errors when writing files
* Fix #5344: Ignore EOPNOTSUPP errors for extended attributes
* Fix #5421: Fix rare crash if directory is removed during backup
* Fix #5429: Stop retrying uploads when rest-server runs out of space
* Fix #5467: Improve handling of download retries in check command
Details
* Bugfix #5324: Correctly handle backup --stdin-filename with directory paths
In restic 0.18.0, the backup command failed if a filename that includes at least a directory was passed to --stdin-filename. For example, --stdin-filename /foo/bar resulted in the following error:
Fatal: unable to save snapshot: open /foo: no such file or directory
This has now been fixed.
#5324 #5356
* Bugfix #5325: Accept RESTIC_HOST environment variable in forget command
The forget command did not use the host name from the RESTIC_HOST environment variable when filtering snapshots. This has now been fixed.
#5325 #5327
* Bugfix #5342: Ignore "chmod not supported" errors when writing files
Restic 0.18.0 introduced a bug that caused chmod xxx: operation not supported errors to appear when writing to a local file repository that did not support chmod (like CIFS or WebDAV mounted via FUSE). Restic now ignores those errors.
#5342
* Bugfix #5344: Ignore EOPNOTSUPP errors for extended attributes
Restic 0.18.0 added extended attribute support for NetBSD 10+, but not all NetBSD filesystems support extended attributes. Other BSD systems can likewise return EOPNOTSUPP, so restic now ignores these errors.
#5344
* Bugfix #5421: Fix rare crash if directory is removed during backup
In restic 0.18.0, the backup command could crash if a directory was removed between reading its metadata and listing its directory content. This has now been fixed.
#5421
* Bugfix #5429: Stop retrying uploads when rest-server runs out of space
When rest-server returns a 507 Insufficient Storage error, it indicates that no more storage capacity is available. Restic now correctly stops retrying uploads in this case.
#5429 #5452
* Bugfix #5467: Improve handling of download retries in check command
In very rare cases, the check command could unnecessarily report repository damage if the backend returned incomplete, corrupted data on the first download try which is afterwards resolved by a download retry.
This could result in an error output like the following:
Load(<data/34567890ab>, 33918928, 0) returned error, retrying after 871.35598ms: readFull: unexpected EOF Load(<data/34567890ab>, 33918928, 0) operation successful after 1 retries check successful on second attempt, original error pack 34567890ab[...] contains 6 errors: [blob 12345678[...]: decrypting blob <data/12345678> from 34567890 failed: ciphertext verification failed ...] [...] Fatal: repository contains errors
This fix only applies to a very specific case where the log shows operation successful after 1 retries followed by a check successful on second attempt, original error that only reports ciphertext verification failed errors in the pack file. If any other errors are reported in the pack file, then the repository still has to be considered as damaged.
Now, only the check result of the last download retry is reported as intended.
#5467 #5495
Assets 31
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 28 kapsiR, qappell, BackSpace54, antonko, siccovansas, pepperbob, liv-io, 239, FHU-yezi, alexycodes, and 18 more reacted with thumbs up emoji 🎉 19 moritzdietz, RomelSan, Worty, omasanori, qappell, sokai, BackSpace54, siccovansas, szenti, riscie, and 9 more reacted with hooray emoji ❤️ 30 mikix, oliverklee, 56k-modem, konidev20, firescry, jacquesh, nderambure, ImranR98, baekis1185, qappell, and 20 more reacted with heart emoji 🚀 12 moritzdietz, Granshmeyr, mh81, qappell, svengreb, sokai, santiagobiali, siccovansas, brandon-welsch, sebadamus, and 2 more reacted with rocket emoji
All reactions
* 👍 28 reactions
* 🎉 19 reactions
* ❤️ 30 reactions
* 🚀 12 reactions
58 people reacted
restic 0.18.0
restic 0.18.0
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 27 Mar 19:34
v0.18.0
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
d401ad6
Changelog for restic 0.18.0 (2025-03-27)
The following sections list the changes in restic 0.18.0 relevant to restic users. The changes are ordered by importance.
Summary
* Sec #5291: Mitigate attack on content-defined chunking algorithm
* Fix #1843: Correctly restore long filepaths' timestamp on old Windows
* Fix #2165: Ignore disappeared backup source files
* Fix #5153: Include root tree when searching using find --tree
* Fix #5169: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot
* Fix #5212: Fix duplicate data handling in prune --max-unused
* Fix #5249: Fix creation of oversized index by repair index --read-all-packs
* Fix #5259: Fix rare crash in command output
* Chg #4938: Update dependencies and require Go 1.23 or newer
* Chg #5162: Promote feature flags
* Enh #1378: Add JSON support to check command
* Enh #2511: Support generating shell completions to stdout
* Enh #3697: Allow excluding online-only cloud files (e.g. OneDrive)
* Enh #4179: Add sort option to ls command
* Enh #4433: Change default sort order for find output
* Enh #4521: Add support for Microsoft Blob Storage access tiers
* Enh #4942: Add snapshot summary statistics to rewritten snapshots
* Enh #4948: Format exit errors as JSON when requested
* Enh #4983: Add SLSA provenance to GHCR container images
* Enh #5054: Enable compression for ZIP archives in dump command
* Enh #5081: Add retry mechanism for loading repository config
* Enh #5089: Allow including/excluding extended file attributes during restore
* Enh #5092: Show count of deleted files and directories during restore
* Enh #5109: Make small pack size configurable for prune
* Enh #5119: Add start and end timestamps to backup JSON output
* Enh #5131: Add DragonFlyBSD support
* Enh #5137: Make tag command print which snapshots were modified
* Enh #5141: Provide clear error message if AZURE_ACCOUNT_NAME is not set
* Enh #5173: Add experimental S3 cold storage support
* Enh #5174: Add xattr support for NetBSD 10+
* Enh #5251: Improve retry handling for flaky rclone backends
* Enh #52897: Make recover automatically rebuild index when needed
Details
* Security #5291: Mitigate attack on content-defined chunking algorithm
Restic uses Rabin Fingerprints for its content-defined chunker. The algorithm relies on a secret polynomial to split files into chunks.
As shown in the paper "Chunking Attacks on File Backup Services using Content-Defined Chunking" by Boris Alexeev, Colin Percival and Yan X Zhang, an attacker that can observe chunk sizes for a known file can derive the secret polynomial. Knowledge of the polynomial might in some cases allow an attacker to check whether certain large files are stored in a repository.
A practical attack is nevertheless hard as restic merges multiple chunks into opaque pack files and by default processes multiple files in parallel. This likely prevents an attacker from matching pack files to the attacker-known file and thereby prevents the attack.
Despite the low chances of a practical attack, restic now has added mitigation that randomizes how chunks are assembled into pack files. This prevents attackers from guessing which chunks are part of a pack file and thereby prevents learning the chunk sizes.
#5291 #5295
* Bugfix #1843: Correctly restore long filepaths' timestamp on old Windows
The restore command now correctly restores timestamps for files with paths longer than 256 characters on Windows versions prior to Windows 10 1607.
#1843 #5061
* Bugfix #2165: Ignore disappeared backup source files
The backup command now quietly skips files that are removed between directory listing and backup, instead of printing errors like:
error: lstat /some/file/name: no such file or directory
#2165 #3098 #5143 #5145
* Bugfix #5153: Include root tree when searching using find --tree
The restic find --tree command did not find trees referenced by restic snapshot --json. It now correctly includes the root tree when searching.
#5153
* Bugfix #5169: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot
When running backup with the --use-fs-snapshot option in Windows with admin rights, event logs like
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied. . This is often caused by incorrect security settings in either the writer or requester process. Operation: Gathering Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {54b151ac-d27d-4628-9cb0-2bc40959f50f}
Are created several times even though the backup itself succeeds. This has now been fixed.
#5169 #5170 https://forum.restic.net/t/windows-shadow-copy-snapshot-vss-unexpected-provider-error/3674/2
* Bugfix #5212: Fix duplicate data handling in prune --max-unused
The prune --max-unused size command did not correctly account for duplicate data. If a repository contained a large amount of duplicate data, this could previously result in pruning too little data. This has now been fixed.
#5212 https://forum.restic.net/t/restic-not-obeying-max-unused-parameter-on-prune/8879
* Bugfix #5249: Fix creation of oversized index by repair index --read-all-packs
Since restic 0.17.0, the new index created by repair index --read-all-packs was written as a single large index. This significantly increased memory usage while loading the index.
The index is now correctly split into multiple smaller indexes, and repair index now also automatically splits oversized indexes.
#5249
* Bugfix #5259: Fix rare crash in command output
Some commands could in rare cases crash when trying to print status messages and request retries at the same time, resulting in an error like the following:
panic: runtime error: slice bounds out of range [468:156] [...] github.com/restic/restic/internal/ui/termstatus.(*lineWriter).Write(...) /restic/internal/ui/termstatus/stdio_wrapper.go:36 +0x136
This has now been fixed.
#5259 #5300
* Change #4938: Update dependencies and require Go 1.23 or newer
We have updated all dependencies. Restic now requires Go 1.23 or newer to build.
This also disables support for TLS versions older than TLS 1.2. On Windows, restic now requires at least Windows 10 or Windows Server 2016. On macOS, restic now requires at least macOS 11 Big Sur.
#4938
* Change #5162: Promote feature flags
The deprecate-legacy-index, deprecate-s3-legacy-layout, explicit-s3-anonymous-auth and safe-forget-keep-tags features are now stable and can no longer be disabled. The corresponding feature flags will be removed in restic 0.19.0.
#5162
* Enhancement #1378: Add JSON support to check command
The check command now supports the --json option to output all statistics in JSON format.
#1378 #5194
* Enhancement #2511: Support generating shell completions to stdout
The generate command now supports using - as the filename with the --[shell]-completion option to ...
Read more
Assets 31
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 37 BackSpace54, drdeimos, eugenesan, jmigual, vmlemon, xplosionmind, RT2Code, Safari77, jinhao-huang, liv-io, and 27 more reacted with thumbs up emoji 🎉 20 BackSpace54, wheelercj, svengreb, apa4h, joshuachp, mortaza-uroc, maxwassiljew, jee-r, FHU-yezi, croissong, and 10 more reacted with hooray emoji ❤️ 32 jedi453, jmigual, vmlemon, xplosionmind, Toflar, apa4h, 56k-modem, peterhirn, tobifroe, joshuachp, and 22 more reacted with heart emoji 🚀 14 svengreb, vmlemon, xplosionmind, joshuachp, croissong, alexbarton, nadir-ishiguro, santiagobiali, patrickwolf, rob4226, and 4 more reacted with rocket emoji
All reactions
* 👍 37 reactions
* 🎉 20 reactions
* ❤️ 32 reactions
* 🚀 14 reactions
59 people reacted
restic 0.17.3
restic 0.17.3
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 08 Nov 19:52
v0.17.3
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
bc64921
Changelog for restic 0.17.3 (2024-11-08)
The following sections list the changes in restic 0.17.3 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #4971: Fix unusable mount on macOS Sonoma
* Fix #5003: Fix metadata errors during backup of removable disks on Windows
* Fix #5101: Do not retry load/list operation if SFTP connection is broken
* Fix #5107: Fix metadata error on Windows for backups using VSS
* Enh #5096: Allow prune --dry-run without lock
Details
* Bugfix #4971: Fix unusable mount on macOS Sonoma
On macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved.
#4971 #5048
* Bugfix #5003: Fix metadata errors during backup of removable disks on Windows
Since restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below.
error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.
This has now been fixed.
#5003 #5123 https://forum.restic.net/t/backing-up-a-folder-from-a-veracrypt-volume-brings-up-errors-since-restic-v17-0/8444
* Bugfix #5101: Do not retry load/list operation if SFTP connection is broken
When using restic with the SFTP backend, backend operations that load a file or list files were retried even if the SFTP connection was broken. This has now been fixed.
#5101 https://forum.restic.net/t/restic-hanging-on-backup/8559
* Bugfix #5107: Fix metadata error on Windows for backups using VSS
Since restic 0.17.2, when creating a backup on Windows using --use-fs-snapshot, restic would report an error like the following:
error: incomplete metadata for C:\: get EA failed while opening file handle for path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyXX\, with: The process cannot access the file because it is being used by another process.
This has now been fixed by correctly handling paths that refer to volume shadow copy snapshots.
#5107 #5110 #5112
* Enhancement #5096: Allow prune --dry-run without lock
The prune --dry-run --no-lock now allows performing a dry-run without locking the repository. Note that if the repository is modified concurrently, prune may return inaccurate statistics or errors.
#5096
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 23 BackSpace54, pertsevds, zicklag, fgimian, RT2Code, dimlev, seqizz, adrian5, firengate, alanorth, and 13 more reacted with thumbs up emoji 😄 1 firengate reacted with laugh emoji 🎉 7 BackSpace54, santiagobiali, firengate, OidaTiftla, kekscode, askielboe-flextribe, and siccovansas reacted with hooray emoji ❤️ 14 oliverklee, dimlev, firescry, wopfel, firengate, 239, CompuRoot, croissong, askielboe-flextribe, tgrothe, and 4 more reacted with heart emoji 🚀 9 oliverklee, santiagobiali, alexbarton, akrabu, RT2Code, firengate, askielboe-flextribe, szenti, and siccovansas reacted with rocket emoji 👀 3 Lencerf, firengate, and xplosionmind reacted with eyes emoji
All reactions
* 👍 23 reactions
* 😄 1 reaction
* 🎉 7 reactions
* ❤️ 14 reactions
* 🚀 9 reactions
* 👀 3 reactions
35 people reacted
restic 0.17.2
restic 0.17.2
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 27 Oct 15:55
v0.17.2
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
2fb07dc
Changelog for restic 0.17.2 (2024-10-27)
The following sections list the changes in restic 0.17.2 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #4004: Support container-level SAS/SAT tokens for Azure backend
* Fix #5047: Resolve potential error during concurrent cache cleanup
* Fix #5050: Return error if tag fails to lock repository
* Fix #5057: Exclude irregular files from backups
* Fix #5063: Correctly backup extended metadata when using VSS on Windows
Details
* Bugfix #4004: Support container-level SAS/SAT tokens for Azure backend
Restic previously expected SAS/SAT tokens to be generated at the account level, which prevented tokens created at the container level from being used to initialize a repository. This caused an error when attempting to initialize a repository with container-level tokens.
Restic now supports both account-level and container-level SAS/SAT tokens for initializing a repository.
#4004 #5093
* Bugfix #5047: Resolve potential error during concurrent cache cleanup
When multiple restic processes ran concurrently, they could compete to remove obsolete snapshots from the local backend cache, sometimes leading to a "no such file or directory" error. Restic now suppresses this error to prevent issues during cache cleanup.
#5047
* Bugfix #5050: Return error if tag fails to lock repository
Since restic 0.17.0, the tag command did not return an error when it failed to open or lock the repository. This issue has now been fixed.
#5050 #5056
* Bugfix #5057: Exclude irregular files from backups
Since restic 0.17.1, files with the type irregular could mistakenly be included in snapshots, especially when backing up special file types on Windows that restic cannot process. This issue has now been fixed.
Previously, this bug caused the check command to report errors like the following one:
tree 12345678[...]: node "example.zip" with invalid type "irregular"
To repair affected snapshots, upgrade to restic 0.17.2 and run:
restic repair snapshots --forget
This will remove the irregular files from the snapshots (creating a new snapshot ID for each of the affected snapshots).
#5057 https://forum.restic.net/t/errors-found-by-check-1-invalid-type-irregular-2-ciphertext-verification-failed/8447/2
* Bugfix #5063: Correctly backup extended metadata when using VSS on Windows
On Windows, when creating a backup with the --use-fs-snapshot option, restic read extended metadata from the original filesystem path instead of from the snapshot. This could result in errors if files were removed during the backup process.
This issue has now been resolved.
#5063 #5097 #5099
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 23 hepptho, Safari77, onedr0p, liv-io, fgimian, bkis, kapsiR, pymq, xplosionmind, 239, and 13 more reacted with thumbs up emoji 😄 1 firengate reacted with laugh emoji 🎉 4 santiagobiali, firengate, clyvari, and siccovansas reacted with hooray emoji ❤️ 14 oliverklee, 56k-modem, pertsevds, onedr0p, pymq, firescry, xplosionmind, 239, santiagobiali, firengate, and 4 more reacted with heart emoji 🚀 6 alexbarton, santiagobiali, frzifus, firengate, adrian5, and siccovansas reacted with rocket emoji 👀 2 firengate and ilium007 reacted with eyes emoji
All reactions
* 👍 23 reactions
* 😄 1 reaction
* 🎉 4 reactions
* ❤️ 14 reactions
* 🚀 6 reactions
* 👀 2 reactions
31 people reacted
restic 0.17.1
restic 0.17.1
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 05 Sep 19:41
v0.17.1
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
975aa41
Changelog for restic 0.17.1 (2024-09-05)
The following sections list the changes in restic 0.17.1 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #2004: Correctly handle volume names in backup command on Windows
* Fix #4945: Include missing backup error text with --json
* Fix #4953: Correctly handle long paths on older Windows versions
* Fix #4957: Fix delayed cancellation of certain commands
* Fix #4958: Don't ignore metadata-setting errors during restore
* Fix #4969: Correctly restore timestamp for files with resource forks on macOS
* Fix #4975: Prevent backup --stdin-from-command from panicking
* Fix #4980: Skip extended attribute processing on unsupported Windows volumes
* Fix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error
* Fix #5005: Fix rare failures to retry locking a repository
* Fix #5018: Improve HTTP/2 support for REST backend
* Chg #4953: Also back up files with incomplete metadata
* Enh #4795: Display progress bar for restore --verify
* Enh #4934: Automatically clear removed snapshots from cache
* Enh #4944: Print JSON-formatted errors during restore --json
* Enh #4959: Return exit code 12 for "bad password" errors
* Enh #4970: Make timeout for stuck requests customizable
Details
* Bugfix #2004: Correctly handle volume names in backup command on Windows
On Windows, when the specified backup target only included the volume name without a trailing slash, for example, C:, then restoring the resulting snapshot would result in an error. Note that using C:\ as backup target worked correctly.
Specifying volume names is now handled correctly. To restore snapshots created before this bugfix, use the : syntax. For example, to restore a snapshot with ID 12345678 that backed up C:, use the following command:
restic restore 12345678:/C/C:./ --target output/folder
#2004 #5028
* Bugfix #4945: Include missing backup error text with --json
Previously, when running a backup with the --json option, restic failed to include the actual error message in the output, resulting in "error": {} being displayed.
This has now been fixed, and restic now includes the error text in JSON output.
#4945 #4946
* Bugfix #4953: Correctly handle long paths on older Windows versions
On older Windows versions, like Windows Server 2012, restic 0.17.0 failed to back up files with long paths. This problem has now been resolved.
#4953 #4954
* Bugfix #4957: Fix delayed cancellation of certain commands
Since restic 0.17.0, some commands did not immediately respond to cancellation via Ctrl-C (SIGINT) and continued running for a short period. The most affected commands were diff,find, ls, stats and rewrite. This is now resolved.
#4957 #4960
* Bugfix #4958: Don't ignore metadata-setting errors during restore
Previously, restic used to ignore errors when setting timestamps, attributes, or file modes during a restore. It now reports those errors, except for permission related errors when running without root privileges.
#4958
* Bugfix #4969: Correctly restore timestamp for files with resource forks on macOS
On macOS, timestamps were not restored for files with resource forks. This has now been fixed.
#4969 #5006
* Bugfix #4975: Prevent backup --stdin-from-command from panicking
Restic would previously crash if --stdin-from-command was specified without providing a command. This issue has now been fixed.
#4975 #4976
* Bugfix #4980: Skip extended attribute processing on unsupported Windows volumes
With restic 0.17.0, backups of certain Windows paths, such as network drives, failed due to errors while fetching extended attributes.
Restic now skips extended attribute processing for volumes where they are not supported.
#4955 #4950 #4980 #4998
* Bugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error
On Windows, creating a backup could sometimes trigger the following error:
error: nodeFromFileInfo [...]: get named security info failed with: a required privilege is not held by the client.
This has now been fixed.
#5004 #5019
* Bugfix #5005: Fix rare failures to retry locking a repository
Restic 0.17.0 could in rare cases fail to retry locking a repository if one of the lock files failed to load, resulting in the error:
unable to create lock in backend: circuit breaker open for file <lock/1234567890>
This issue has now been addressed. The error handling now properly retries the locking operation. In addition, restic waits a few seconds between locking retries to increase chances of successful locking.
#5005 #5011 #5012
* Bugfix #5018: Improve HTTP/2 support for REST backend
If rest-server tried to gracefully shut down an HTTP/2 connection still in use by the client, it could result in the following error:
http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
This issue has now been resolved.
#5018 https://forum.restic.net/t/receiving-http2-goaway-messages-with-windows-restic-v0-17-0/8367
* Change #4953: Also back up files with incomplete metadata
If restic failed to read extended metadata for a file or folder during a backup, then the file or folder was not included in the resulting snapshot. Instead, a warning message was printed along with returning exit code 3 once the backup was finished.
Now, restic also includes items for which the extended metadata could not be read in a snapshot. The warning message has been updated to:
incomplete metadata for /path/to/file: <details about error>
#4953 #4977
* Enhancement #4795: Display progress bar for restore --verify
When the restore command is run with --verify, it now displays a progress bar while the verification step is running. The progress bar is not shown when the --json flag is specified.
#4795 #4989
* Enhancement #4934: Automatically clear removed snapshots from cache
Previously, restic only removed snapshots from the cache on the host where the forget command was executed. On other hosts that use the same repository, the old snapshots remained in the cache.
Restic now automatically clears old snapshots from the local cache of the current host.
#4934 #4981
* Enhancement #4944: Print JSON-formatted errors during restore --json
Restic used to print any restore errors directly to the console as freeform text messages, even when using the --json option.
Now, when --json is specified, restic prints them as JSON formatted messages.
#4944 #4946
* Enhancement #4959: Return exit code 12 for "bad password" errors
Restic now returns exit code 12 when it cannot open the repository due to an incorrect password.
#4959
* Enhancement #4970: Make timeout for stuck requests customizable
Restic monitors connections to the backend to detect stuck requests. If a request does not return any data within five minutes, restic assumes the request is stuck and retries it. However, for large repositories this timeout might be insufficient to collect a list of all files, causing the following error:
`List(data) returned error,...
Read more
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 19 war59312, watsonbox, xplosionmind, stevleibelt, hepptho, liv-io, adrian5, abno85, firengate, bronsen, and 9 more reacted with thumbs up emoji 😄 2 firengate and Tbombs reacted with laugh emoji 🎉 8 davehope, ebits21, firengate, santiagobiali, Tbombs, YouDoMeIDoYou, rob4226, and siccovansas reacted with hooray emoji ❤️ 20 56k-modem, kapsiR, tfeldmann, wiserain, firescry, xplosionmind, mikix, apawelec, tobifroe, oliverklee, and 10 more reacted with heart emoji 🚀 7 firengate, spezifisch, santiagobiali, Tbombs, alexbarton, rob4226, and siccovansas reacted with rocket emoji 👀 4 xplosionmind, Safari77, firengate, and Tbombs reacted with eyes emoji
All reactions
* 👍 19 reactions
* 😄 2 reactions
* 🎉 8 reactions
* ❤️ 20 reactions
* 🚀 7 reactions
* 👀 4 reactions
39 people reacted
restic 0.17.0
restic 0.17.0
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 26 Jul 09:45
v0.17.0
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
277c8f5
Changelog for restic 0.17.0 (2024-07-26)
The following sections list the changes in restic 0.17.0 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #3600: Handle unreadable xattrs in folders above backup source
* Fix #4209: Fix slow SFTP upload performance
* Fix #4503: Correct hardlink handling in stats command
* Fix #4568: Prevent forget --keep-tags <invalid> from deleting all snapshots
* Fix #4615: Make find not sometimes ignore directories
* Fix #4656: Properly report ID of newly added keys
* Fix #4703: Shutdown cleanly when receiving SIGTERM
* Fix #4709: Correct --no-lock handling of ls and tag commands
* Fix #4760: Fix possible error on concurrent cache cleanup
* Fix #4850: Handle UTF-16 password files in key command correctly
* Fix #4902: Update snapshot summary on rewrite
* Chg #956: Return exit code 10 and 11 for non-existing and locked repository
* Chg #4540: Require at least ARMv6 for ARM binaries
* Chg #4602: Deprecate legacy index format and s3legacy repository layout
* Chg #4627: Redesign backend error handling to improve reliability
* Chg #4707: Disable S3 anonymous authentication by default
* Chg #4744: Include full key ID in JSON output of key list
* Enh #662: Optionally skip snapshot creation if nothing changed
* Enh #693: Include snapshot size in snapshots output
* Enh #805: Add bitrot detection to diff command
* Enh #828: Improve features of the repair packs command
* Enh #1786: Support repositories with empty password
* Enh #2348: Add --delete option to restore command
* Enh #3067: Add extended options to configure Windows Shadow Copy Service
* Enh #3406: Improve dump performance for large files
* Enh #3806: Optimize and make prune command resumable
* Enh #4006: (alpha) Store deviceID only for hardlinks
* Enh #4048: Add support for FUSE-T with mount on macOS
* Enh #4251: Support reading backup from a command's standard output
* Enh #4287: Support connection to rest-server using unix socket
* Enh #4354: Significantly reduce prune memory usage
* Enh #4437: Make check command create non-existent cache directory
* Enh #4472: Support AWS Assume Role for S3 backend
* Enh #4547: Add --json option to version command
* Enh #4549: Add --ncdu option to ls command
* Enh #4573: Support rewriting host and time metadata in snapshots
* Enh #4583: Ignore s3.storage-class archive tiers for metadata
* Enh #4590: Speed up mount command's error detection
* Enh #4601: Add support for feature flags
* Enh #4611: Back up more file metadata on Windows
* Enh #4664: Make ls use message_type field in JSON output
* Enh #4676: Make key command's actions separate sub-commands
* Enh #4678: Add --target option to the dump command
* Enh #4708: Back up and restore SecurityDescriptors on Windows
* Enh #4733: Allow specifying --host via environment variable
* Enh #4737: Include snapshot ID in reason field of forget JSON output
* Enh #4764: Support forgetting all snapshots
* Enh #4768: Allow specifying custom User-Agent for outgoing requests
* Enh #4781: Add restore options to read include/exclude patterns from files
* Enh #4807: Support Extended Attributes on Windows NTFS
* Enh #4817: Make overwrite behavior of restore customizable
* Enh #4839: Add dry-run support to restore command
Details
* Bugfix #3600: Handle unreadable xattrs in folders above backup source
When backup sources are specified using absolute paths, backup also includes information about the parent folders of the backup sources in the snapshot.
If the extended attributes for some of these folders could not be read due to missing permissions, this caused the backup to fail. This has now been fixed.
#3600 #4668 https://forum.restic.net/t/parent-directories-above-the-snapshot-source-path-fatal-error-permission-denied/7216
* Bugfix #4209: Fix slow SFTP upload performance
Since restic 0.12.1, the upload speed of the sftp backend to a remote server has regressed significantly. This has now been fixed.
#4209 #4782
* Bugfix #4503: Correct hardlink handling in stats command
If files on different devices had the same inode ID, the stats command did not correctly calculate the snapshot size. This has now been fixed.
#4503 #4006 https://forum.restic.net/t/possible-bug-in-stats/6461/8
* Bugfix #4568: Prevent forget --keep-tags <invalid> from deleting all snapshots
Running forget --keep-tags <invalid>, where <invalid> is a tag that does not exist in the repository, would remove all snapshots. This is especially problematic if the tag name contains a typo.
The forget command now fails with an error if all snapshots in a snapshot group would be deleted. This prevents the above example from deleting all snapshots.
It is possible to temporarily disable the new check by setting the environment variable RESTIC_FEATURES=safe-forget-keep-tags=false. Note that this feature flag will be removed in the next minor restic version.
#4568 #4764
* Bugfix #4615: Make find not sometimes ignore directories
In some cases, the find command ignored empty or moved directories. This has now been fixed.
#4615
* Bugfix #4656: Properly report ID of newly added keys
restic key add now reports the ID of the newly added key. This simplifies selecting a specific key using the --key-hint key option.
#4656 #4657
* Bugfix #4703: Shutdown cleanly when receiving SIGTERM
Previously, when restic received the SIGTERM signal it would terminate immediately, skipping cleanup and potentially causing issues like stale locks being left behind. This primarily effected containerized restic invocations that use SIGTERM, but could also be triggered via a simple killall restic.
This has now been fixed, such that restic shuts down cleanly when receiving the SIGTERM signal.
#4703
* Bugfix #4709: Correct --no-lock handling of ls and tag commands
The ls command never locked the repository. This has now been fixed, with the old behavior still being supported using ls --no-lock. The latter invocation also works with older restic versions.
The tag command erroneously accepted the --no-lock command. This command now always requires an exclusive lock.
#4709
* Bugfix #4760: Fix possible error on concurrent cache cleanup
If multiple restic processes concurrently cleaned up no longer existing files from the cache, this could cause some of the processes to fail with an no such file or directory error. This has now been fixed.
#4760 #4761...
Read more
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 42 Safari77, firengate, BackSpace54, JManch, dominikschulz, SmartFinn, liv-io, haunt98, abobov, ebta, and 32 more reacted with thumbs up emoji 😄 4 firengate, haunt98, ebta, and directentis1 reacted with laugh emoji 🎉 13 firengate, BackSpace54, davehope, meise, tmeckel, tmlmt, joelvaneenwyk, alexbarton, djds, mholt, and 3 more reacted with hooray emoji ❤️ 26 apawelec, adrianclm, firengate, oliverklee, stephan2012, seqizz, mikix, firescry, ebta, 239, and 16 more reacted with heart emoji 🚀 19 firengate, themilkman, seqizz, ebta, astra1701, strayer, dassump, mrksmrtn, meise, tmeckel, and 9 more reacted with rocket emoji 👀 2 xplosionmind and directentis1 reacted with eyes emoji
All reactions
* 👍 42 reactions
* 😄 4 reactions
* 🎉 13 reactions
* ❤️ 26 reactions
* 🚀 19 reactions
* 👀 2 reactions
76 people reacted
restic 0.16.5
restic 0.16.5
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 01 Jul 19:42
v0.16.5
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
fe9f142
Changelog for restic 0.16.5 (2024-07-01)
The following sections list the changes in restic 0.16.5 relevant to restic users. The changes are ordered by importance.
Summary
* Enh #4799: Add option to force use of Azure CLI credential
* Enh #4873: Update dependencies
Details
* Enhancement #4799: Add option to force use of Azure CLI credential
A new environment variable AZURE_FORCE_CLI_CREDENTIAL=true allows forcing the use of Azure CLI credential, ignoring other credentials like managed identity.
#4799
* Enhancement #4873: Update dependencies
A few potentially vulnerable dependencies were updated.
#4873 #4878
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 19 BackSpace54, cpuschma, kapsiR, stevleibelt, azzamsa, liv-io, tmeckel, firengate, JoshuaPettus, adrian5, and 9 more reacted with thumbs up emoji 😄 4 creativeprojects, smbl64, firengate, and fred2a reacted with laugh emoji 🎉 9 BackSpace54, dmotte, ImranR98, tmeckel, Red-Clay, firengate, Aqaao, kennedn, and grisu48 reacted with hooray emoji ❤️ 13 jedi453, 56k-modem, Safari77, mikaoioi, creativeprojects, dmotte, bkis, TwizzyDizzy, firengate, 239, and 3 more reacted with heart emoji 🚀 8 dassump, Nkmol, mrksmrtn, akrabu, dmotte, tmeckel, alexbarton, and firengate reacted with rocket emoji 👀 1 seqizz reacted with eyes emoji
All reactions
* 👍 19 reactions
* 😄 4 reactions
* 🎉 9 reactions
* ❤️ 13 reactions
* 🚀 8 reactions
* 👀 1 reaction
41 people reacted
restic 0.16.4
restic 0.16.4
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
fd0 released this 04 Feb 19:18
v0.16.4
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
3786536
This release works around and improves detection of a bug in the compression library used by restic. The resulting issue only happens when using restic 0.16.3 and the max compression level (the default auto and off compression levels are not affected), and when the source files being backed up have specific data in them to trigger the bug. If you use max compression, you can use restic check --read-data to make sure you're not affected.
restic is distributed as a standalone binary: download the correct file for your operating system and architecture, extract the file and just run it. If you run into any issues, please report them at the GitHub issue tracker or visit the forum. If you already have restic >= 0.9.4, you can use restic self-update to get the latest version in a secure way.
The binaries released with each restic version are reproducible, which means that you can reproduce a byte identical version from the source code for that release. Instructions on how to do that in the Developer Documentation.
Changelog for restic 0.16.4 (2024-02-04)
The following sections list the changes in restic 0.16.4 relevant to restic users. The changes are ordered by importance.
Summary
* Fix #4677: Downgrade zstd library to fix rare data corruption at max. compression
* Enh #4529: Add extra verification of data integrity before upload
Details
* Bugfix #4677: Downgrade zstd library to fix rare data corruption at max. compression
In restic 0.16.3, backups where the compression level was set to max (using --compression max) could in rare and very specific circumstances result in data corruption due to a bug in the library used for compressing data. Restic 0.16.1 and 0.16.2 were not affected.
Restic now uses the previous version of the library used to compress data, the same version used by restic 0.16.2. Please note that the auto compression level (which restic uses by default) was never affected, and even if you used max compression, chances of being affected by this issue are small.
To check a repository for any corruption, run restic check --read-data. This will download and verify the whole repository and can be used at any time to completely verify the integrity of a repository. If the check command detects anomalies, follow the suggested steps.
#4677 #4679
* Enhancement #4529: Add extra verification of data integrity before upload
Hardware issues, or a bug in restic or its dependencies, could previously cause corruption in the files restic created and stored in the repository. Detecting such corruption previously required explicitly running the check --read-data or check --read-data-subset commands.
To further ensure data integrity, even in the case of hardware issues or software bugs, restic now performs additional verification of the files about to be uploaded to the repository.
These extra checks will increase CPU usage during backups. They can therefore, if absolutely necessary, be disabled using the --no-extra-verify global option. Please note that this should be combined with more active checking using the previously mentioned check commands.
#4529 #4681
Assets 30
Loading
Uh oh!
There was an error while loading. Please reload this page.
👍 28 Onurtag, BackSpace54, kossmac, croissong, ligurio, 4rne, onedr0p, Nkmol, firengate, generalworksinc, and 18 more reacted with thumbs up emoji 🎉 4 voronin9032, danyreyna, ImranR98, and guycalledseven reacted with hooray emoji ❤️ 23 oliverklee, 4rne, meise, thushan, onedr0p, shd2h, larouxn, firengate, Safari77, kevnox, and 13 more reacted with heart emoji 🚀 1 kinbod reacted with rocket emoji 👀 2 simonemargio and onedr0p reacted with eyes emoji
All reactions
* 👍 28 reactions
* 🎉 4 reactions
* ❤️ 23 reactions
* 🚀 1 reaction
* 👀 2 reactions
46 people reacted
Previous 1 2 3 4 5 6 Next
Previous Next
Footer
© 2026 GitHub, Inc.
Footer navigation
* Terms
* Privacy
* Security
* Status
* Community
* Docs
* Contact
* Manage cookies
* Do not share my personal information
You can’t perform that action at this time.
Derzeit werden Unterschiede nur textuell und nicht grafisch dargestellt, es ist nur der letzte Screenshot verfügbar.
Für Screenshots ist ein Content Fetcher (Sockpuppetbrowser, Selenium usw.) erforderlich, der Screenshots unterstützt.