Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-12-02 | build_man1.2.7 | Thomas Waldmann | |
2023-12-02 | build_usage | Thomas Waldmann | |
2023-12-02 | update CHANGES | Thomas Waldmann | |
2023-12-02 | docs: Add "check.rebuild_refcounts" message | Sophie Herold | |
2023-11-29 | Merge pull request #7952 from ThomasWaldmann/update-changes-1.2 | TW | |
update CHANGES (1.2-maint) | |||
2023-11-27 | Remove period that could be interpreted as part of the command (#7946) | Kevin Yin | |
CVE upgrade steps: remove period that could be interpreted as part of the command | |||
2023-11-27 | update CHANGES | Thomas Waldmann | |
2023-11-13 | Add backup by SERIAL method (#7934) | zDEFz | |
docs: create disk/partition sector backup by disk serial number | |||
2023-11-06 | CVE-2023-36811 upgrade docs: consider checkpoint archives, fixes #7802 | Thomas Waldmann | |
The traceback seen there came from borg not showing a .checkpoint archive that didn't have a valid TAM and thus the user not see it / fix it: https://github.com/borgbackup/borg/issues/7802#issuecomment-1793860606 | |||
2023-11-03 | update CHANGES | Thomas Waldmann | |
2023-11-01 | docs: not only attack/unsafe, can also be a fs issue, fixes #7853 | Thomas Waldmann | |
2023-11-01 | docs: point to CVE-2023-36811 upgrade steps from borg 1.1 to 1.2 upgrade ↵ | Thomas Waldmann | |
steps, fixes #7899 also: use 1.2.6 to refer to the fixed version 1.2.5 had issues and was superseded by 1.2.6 just 1 day later, so we do not need to talk about that. Also, the docs point out that: """ Below, if we speak of borg 1.2.6, we mean a borg version >= 1.2.6 **or** a borg version that has the relevant security patches for this vulnerability applied (could be also an older version in that case). """ So, it now just talks about "1.2.6" at the relevant places. | |||
2023-11-01 | docs: upgrade steps needed for all kinds of repos, fixes #7813 | Thomas Waldmann | |
Repos with encryption=none of course can not do real authentication (because there is no secret key material to work with). But the code always works the same way and such repos also use (and expect) TAMs, so the instructions should be followed in any case. | |||
2023-11-01 | docs: consequences of borg check, fixes #7816 | Thomas Waldmann | |
2023-10-27 | Merge pull request #7890 from ThomasWaldmann/doc-updates-1.2 | TW | |
doc updates (1.2-maint) | |||
2023-10-27 | docs: OS X -> macOS | Thomas Waldmann | |
2023-10-27 | docs: update macOS hint about full disk access | Thomas Waldmann | |
2023-10-27 | docs: minor fixes/update to notes | Thomas Waldmann | |
2023-10-27 | docs: remove info about borg 1.0 files per dir | Thomas Waldmann | |
2023-10-27 | docs: no signature upload on pypi any more | Thomas Waldmann | |
but we upload it on github releases, so people can check it. | |||
2023-10-27 | docs: CI only on github actions now | Thomas Waldmann | |
2023-10-27 | automated-local.rst: Partition table UUID match works for MBR too | azrdev | |
not only GPT | |||
2023-10-27 | automated-local.rst: use GPT UUID for consistent udev rule | azrdev | |
2023-09-25 | update CHANGES | Thomas Waldmann | |
2023-09-02 | docs: minor fix to CVE-2023-36811 related upgrade instructions | Thomas Waldmann | |
while the main issue in the code has been fixed since 1.2.5, let's better refer to 1.2.6, which has fixes in upgrade docs and code. | |||
2023-08-31 | update CHANGES, incl. upgrade instructions | Thomas Waldmann | |
2023-08-31 | implement BORG_WORKAROUNDS=ignore_invalid_archive_tam, see #7791 | Thomas Waldmann | |
2023-08-30 | fix changelog markupchangelog-1.2.51.2.5.post1 | Thomas Waldmann | |
2023-08-30 | fix CVE timeline | Thomas Waldmann | |
2023-08-30 | build_usage / build_man1.2.5 | Thomas Waldmann | |
2023-08-30 | update CHANGES | Thomas Waldmann | |
2023-08-30 | document vulnerability, repo upgrade procedure | Thomas Waldmann | |
2023-08-29 | build_man / build_usage | Thomas Waldmann | |
2023-08-29 | update CHANGES | Thomas Waldmann | |
2023-08-24 | docs: fix borg init command in environment.rst.inc | Thomas Waldmann | |
It mentioned borg rcreate due to a bad backport from master. Must be borg init in borg 1.2.x. | |||
2023-07-22 | 1.1.x upgrade notes: more precise borg upgrade instructions, fixes #3396 | Thomas Waldmann | |
2023-07-20 | build_man / build_usage | Thomas Waldmann | |
2023-07-20 | update CHANGES | Thomas Waldmann | |
2023-07-07 | Merge pull request #7702 from ThomasWaldmann/authenticated-no-key-1.2 | TW | |
BORG_WORKAROUNDS=authenticated_no_key, fixes #7700 | |||
2023-07-04 | Merge pull request #7709 from TimWolla/backport-doc-keep-within | TW | |
Backport: Improve the documentation for `--keep-within` | |||
2023-07-04 | Improve the documentation for `--keep-within` | Tim Düsterhus | |
Move the explanation below the general explanation of the `--keep-*` option behavior rephrase the last sentence to make it clear that it works like the other options that were explained in the previous paragraph. Resolves #7687 (cherry picked from commit a6f452a05023621a84a4bdca31b31a6ea0f2b73a) | |||
2023-07-03 | remove coala (outdated) | Thomas Waldmann | |
last coala release (0.11.0) is now over 6y old. when using pip install coala, a ton of stuff gets installed (expected) and a part of that downgrades some stuff we use to outdated, incompatible versions. when trying to run coala with python 3.11, it just crashes because the last release was made for py35/py36 (as seen in their setup.py). a lot of PRs and tickets pile up at the coala project on github, but noone is maintaining it. | |||
2023-07-03 | BORG_WORKAROUNDS=authenticated_no_key to extract from authenticated repos ↵ | Thomas Waldmann | |
without key, fixes #7700 | |||
2023-07-01 | update CHANGES | Thomas Waldmann | |
2023-07-01 | docs: move upgrade notes to own section, see #7546 | Thomas Waldmann | |
2023-07-01 | mount -olocal: how to show mount in finder's sidebar, fixes #5321 | Thomas Waldmann | |
2023-06-27 | list: fix --pattern examples, fixes #7611 | Thomas Waldmann | |
- pattern needs to start with + - ! - first match wins - the default is to list everything, thus a 2nd pattern is needed to exclude everything not matched by 1st pattern. | |||
2023-05-07 | Remove black formatting from cherry-pick | Sasha Boginsky | |
2023-05-05 | Installed and configured pre-commit to lint and format code. Fixes #7476 | Michael Deyaso | |
(cherry picked from commit 98d1c65b404e77756289e32d1ef718318a36ece7) | |||
2023-03-23 | build_man1.2.4 | Thomas Waldmann | |