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 D75CF1FF0C0 for ; Fri, 21 Aug 2026 09:01:32 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 912212153C; Fri, 21 Aug 2026 09:01:31 +0200 (CEST) Message-ID: <218de75e-21db-40da-a2d2-77e06f123d1a@proxmox.com> Date: Fri, 21 Aug 2026 09:01:26 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Native Windows client To: Ciro Iriarte , pbs-devel@lists.proxmox.com References: Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: 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: 1787295660539 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.423 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) 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: DQ3ZCGD24HOGGEEQL5YF2SDMCTYR7SWE X-Message-ID-Hash: DQ3ZCGD24HOGGEEQL5YF2SDMCTYR7SWE 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: Hi, On 8/16/26 5:22 PM, Ciro Iriarte wrote: > Hello, > > I'm working on a native Windows client for PBS, is that something you would > consider adopting as a contribution?. Yes, we definitely welcome bigger code and feature contributions! However, please let me make clear that this comes with some caveats: We cannot accept low effort code contributions, which cannot keep up with expectations and quality assurance and only cause additional burden on review, testing and long term maintenance. Having some deeper understanding in Windows system programming and filesystems is therefore a must. > One thing to consider is that publication would require a yearly paid > certificate and free process with Microsoft to keep Smartscreen and > SecureBoot happy (Windows currently requires signing for both the installer > and kernel modules, WNBD in this case) We do have some capabilities here in house as well, since required for secure boot. Not sure if it would be possible to use this for a windows native client for PBS as well. @Fabian maybe you have more insights and can comment on that? Best regards, Chris