3 ms·

Currently, you can either provide the `BORG_REPO_PERMISSIONS` env var to borg [0] or `--permissions` flag to `borg serve` [1]. You can then enforce this as part

Currently, you can either provide the `BORG_REPO_PERMISSIONS` env var to borg [0] or `--permissions` flag to `borg serve` [1]. You can then enforce this as part of your `authorized_keys` command, for example. [0] https://github.com/borgbackup/borg/blob/3cf8d7cf2f36246ded75de3ddaa4d2ea8191a53e/src/borg/repository.py#L127 https://github.com/borgbackup/borg/blob/3cf8d7cf2f36246ded75... [1] https://github.com/borgbackup/borg/blob/3cf8d7cf2f36246ded75de3ddaa4d2ea8191a53e/src/borg/archiver/serve_cmd.py#L75 https://github.com/borgbackup/borg/blob/3cf8d7cf2f36246ded75...

zargon 1y ago
Ah, I was searching borgstore for no-delete, but it gets exploded into itemized permissions in borg. Documentation seems to be non-existent, as the only mention seems to be the changelog where it suggests this only exists for testing. But I suppose it's not released yet.