From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
dev-internal@internal-list.intra.proxmox.com,
Friedrich Weber <f.weber@proxmox.com>
Cc: w.bumiller@proxmox.com
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 [thread overview]
Message-ID: <178344605109.1458778.472161777807042952.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260706150229.173252-1-f.weber@proxmox.com>
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
parent reply other threads:[~2026-07-07 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260706150229.173252-1-f.weber@proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178344605109.1458778.472161777807042952.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=dev-internal@internal-list.intra.proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.