Merge pull request #9623 from ThomasWaldmann/port-9616-to-master
Some checks are pending
Lint / lint (push) Waiting to run
CI / lint (push) Waiting to run
CI / security (push) Waiting to run
CI / asan_ubsan (push) Blocked by required conditions
CI / native_tests (push) Blocked by required conditions
CI / vm_tests (Haiku, false, haiku, r1beta5) (push) Blocked by required conditions
CI / vm_tests (NetBSD, false, netbsd, 10.1) (push) Blocked by required conditions
CI / vm_tests (OmniOS, false, omnios, r151056) (push) Blocked by required conditions
CI / vm_tests (OpenBSD, false, openbsd, 7.8) (push) Blocked by required conditions
CI / vm_tests (borg-freebsd-14-x86_64-gh, FreeBSD, true, freebsd, 14.3) (push) Blocked by required conditions
CI / windows_tests (push) Blocked by required conditions
CodeQL / Analyze (push) Waiting to run

docs: forward port DoS warning for none mode (fixes #6715)
This commit is contained in:
TW 2026-05-13 13:06:36 +02:00 committed by GitHub
commit 316d774bbd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 6 additions and 2 deletions

View file

@ -614,6 +614,8 @@ b) with ``create --chunker-params buzhash,19,23,21,4095`` (default):
You'll save some memory, but it will need to read / chunk all the files as
it can not skip unmodified files then.
.. _internals_hashindex:
HashIndex
---------

View file

@ -252,6 +252,7 @@ rst_plain_text_references = {
"borg_placeholders": '"borg help placeholders"',
"key_files": "Internals -> Data structures and file formats -> Key files",
"borg_key_export": "borg key export --help",
"internals_hashindex": "Internals -> Data structures and file formats -> HashIndex",
}

View file

@ -157,8 +157,9 @@ class RepoCreateMixIn:
.. nanorst: inline-replace
`none` mode uses no encryption and no authentication. You are advised NOT to use this mode
as it would expose you to all sorts of issues (DoS, confidentiality, tampering, ...) in
case of malicious activity in the repository.
as it would expose you to a Denial-of-Service risk (due to how the :ref:`internals_hashindex`
works) and other issues (confidentiality, tampering, ...) in case of malicious activity
in the repository.
If you do **not** want to encrypt the contents of your backups, but still want to detect
malicious tampering, use an `authenticated` mode. It is like `repokey` minus encryption.