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 1ED021FF146 for ; Tue, 07 Jul 2026 19:41:58 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 28E612143D; Tue, 07 Jul 2026 19:41:57 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, dev-internal@internal-list.intra.proxmox.com, Friedrich Weber Subject: applied: [PATCH proxmox-the-bastion v2] patches: add patch to allow file transfer with PKCS#11-backed keys Date: Tue, 7 Jul 2026 19:41:03 +0200 Message-ID: <178344605109.1458778.472161777807042952.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260706150229.173252-1-f.weber@proxmox.com> References: <20260706150229.173252-1-f.weber@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783446074355 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.017 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: 5UVFYLT4HAFO3CX4ZA4T3DTLGSKBQNVI X-Message-ID-Hash: 5UVFYLT4HAFO3CX4ZA4T3DTLGSKBQNVI X-MailFrom: t.lamprecht@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 CC: w.bumiller@proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 06 Jul 2026 17:02:03 +0200, Friedrich Weber wrote: > Currently, rsync/scp/sftp via the bastion [1] does not work if SSH > egress requires a PIN. This patch adds the possibility to reuse > existing SSH connections for the rsync/scp/sftp sessions without > having to enter the PIN again, and thus makes rsync/scp/sftp possible. > > See inner patch for details. > > [...] Applied, thanks! [1/1] patches: add patch to allow file transfer with PKCS#11-backed keys commit: 2d64f4b7fff9c46c9a782d07fd22267072450e7e