From: Friedrich Weber <f.weber@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH container] vncproxy/termproxy: use SSHInfo helpers
Date: Fri, 10 Jan 2025 18:08:21 +0100 [thread overview]
Message-ID: <7e5907ed-a40b-484e-9ece-8a8b556c6434@proxmox.com> (raw)
In-Reply-To: <20241031101607.84492-1-f.gruenbichler@proxmox.com>
On 31/10/2024 11:16, Fabian Grünbichler wrote:
> to pick up the pinned host keys, instead of relying on them being in the local
> root user's known hosts file.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
applied this patch and
- set up two nodes A and B
- ran container C on B
- navigated to GUI of A
- verified I can access the console of C via xterm.js and noVNC.
Without this patch, both show a SSH key verification prompt.
Consider this:
Tested-by: Friedrich Weber <f.weber@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-01-10 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 10:16 Fabian Grünbichler
2025-01-10 17:08 ` Friedrich Weber [this message]
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=7e5907ed-a40b-484e-9ece-8a8b556c6434@proxmox.com \
--to=f.weber@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox