From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id CB9BB1FF09C for ; Mon, 19 Oct 2026 16:50:48 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A07F52165B; Mon, 19 Oct 2026 16:49:11 +0200 (CEST) From: Christian Ebner To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-backup] docs: mention restricted privileges required for local pull sync jobs Date: Mon, 19 Oct 2026 16:46:49 +0200 Message-ID: <20261019144649.382438-1-c.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1792421225127 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.503 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: ZSWV3SHLPUBPPRVDIFQQ7AKZKXM6JK5Z X-Message-ID-Hash: ZSWV3SHLPUBPPRVDIFQQ7AKZKXM6JK5Z X-MailFrom: c.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Since commit c43aa6ac (""sync: pull: check source datastore/namespace read access) stricter privilege checks are in place for users which create/modify a pull sync job with local source. Mention these restrictions also in the documentation, and discriminate more clearly between pull sync jobs with local and remote source datastore. Signed-off-by: Christian Ebner --- docs/managing-remotes.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst index f1e0ffaa8..0396a9ef1 100644 --- a/docs/managing-remotes.rst +++ b/docs/managing-remotes.rst @@ -102,8 +102,14 @@ trusted remote backup server. To set up sync jobs, the configuring user needs the following permissions: -#. ``Remote.Read`` on the ``/remote/{remote}/{remote-store}`` path -#. At least ``Datastore.Backup`` on the local target datastore (``/datastore/{store}``) +* (Remote Source): ``Remote.Read`` on the ``/remote/{remote}/{remote-store}`` + path for sync jobs when pulling from a remote datastore. +* (Local Source):``Datastore.Audit`` on the local source datastore + ``/datastore/{store}`` and either ``Datastore.Read`` or access to owned backup + groups via ``Datastore.Backup``. For the latter case, if the configuring user + is not the owner of the sync job, ``Datastore.Modify`` is required as well as + this implies changing group ownership. +* At least ``Datastore.Backup`` on the local target datastore (``/datastore/{store}``) .. note:: A sync job can only sync backup groups that the configured remote's user/API token can read. If a remote is configured with a user/API token that -- 2.47.3