Files
borg/docs
Thomas WaldmannandClaude Fable 5.1 26ff43fdcc repo-create: always write config/defaults, so its removal is detected, refs #346
Without the object, the commands silently fell back to the built-in defaults, so
anybody with write access to the store could remove a repository default (e.g. an
"obfuscate" compression) unnoticed: the key protects the content of the object,
not its presence.

Now "borg repo-create" always writes config/defaults (empty if no default was
given), and a missing object is an error (Repository.DefaultsMissing, rc 34) like
one that fails the authentication: the commands using the defaults refuse to run.
"borg check" reports such an object, "borg check --repair" replaces it by empty
defaults, so the repository can be used again (with the built-in defaults).

with_repository reads the defaults only after the security checks (assert_secure).

Co-Authored-By: Claude Fable 5.1 <[email protected]>
2026-09-27 17:09:59 +02:00
..
2025-09-23 14:56:23 +02:00
2026-09-02 21:39:09 +02:00
2026-09-24 15:55:01 +02:00
2026-09-24 15:55:01 +02:00
2016-11-04 21:14:59 -04:00
2025-09-23 14:56:23 +02:00
2025-09-23 14:56:23 +02:00
2026-09-27 15:19:58 +02:00
2026-09-24 22:00:31 +02:00
2026-09-24 15:55:01 +02:00
2025-09-23 14:56:23 +02:00
2026-09-26 12:04:56 +02:00
2025-09-23 14:56:23 +02:00
2025-09-23 14:56:23 +02:00