From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 4FF4C1FF138 for ; Mon, 20 Jul 2026 15:09:30 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 01381214B8; Mon, 20 Jul 2026 15:09:30 +0200 (CEST) Message-ID: <2052bff9-73d8-4cee-9a80-1d93c6dd6996@proxmox.com> Date: Mon, 20 Jul 2026 15:08:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH proxmox{,-backup} 0/3] add flag to opt-in using node proxy config for s3 connections To: pbs-devel@lists.proxmox.com References: <20260511151924.901315-1-c.ebner@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: <20260511151924.901315-1-c.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784552910813 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.415 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_LOW -0.7 Sender listed at https://www.dnswl.org/, low 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: YMSZEJ7BGGDBD4NIQ2I2K426N4NQVF33 X-Message-ID-Hash: YMSZEJ7BGGDBD4NIQ2I2K426N4NQVF33 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: On 5/11/26 5:17 PM, Christian Ebner wrote: > Currently, if set the node proxy config is used unconditionally also > for S3 client API connections. Since this is however not always the > intention, allow users to expliciteley opt-in for individual S3 > endpoint configurations. > > Reported in the community forum: > https://forum.proxmox.com/threads/183436/ gentle ping since the status of this patches was requested in the enterprise support.