public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Koji Nishimura <nsm.kkoji@gmail.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH] fix #6079: use vncticket endpoint for VM serial terminal
Date: Mon, 27 Apr 2026 11:05:58 +0200	[thread overview]
Message-ID: <a8be2fc9-e7d6-4c48-bf3e-84e30d589f29@proxmox.com> (raw)
In-Reply-To: <20260416174046.38591-1-nsm.kkoji@gmail.com>

Hi,

Am 20.04.26 um 4:17 PM schrieb Koji Nishimura:
> Use the vncticket endpoint for the VM serial terminal termproxy path.
> 
> The node shell termproxy path already uses the vncticket endpoint,
> but the VM serial terminal path still uses the older authentication
> flow.
> 
> That older flow prevents VM /termproxy from working with API tokens,
> because authentication fails before the websocket connection can use
> the VNC ticket verification path.
> 
> Make the VM serial terminal path use the same vncticket-based
> authentication flow as the node shell path.
> 
> This fixes the VM /termproxy side of bug 6079. In local testing,
> this was required together with the already-posted access-control
> change for token-owned VNC ticket verification.
> 
> Signed-off-by: Koji Nishimura <nsm.kkoji@gmail.com>
> ---
>  src/PVE/API2/Qemu.pm | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/src/PVE/API2/Qemu.pm b/src/PVE/API2/Qemu.pm
> index 2a1e3854..0b8859fb 100644
> --- a/src/PVE/API2/Qemu.pm
> +++ b/src/PVE/API2/Qemu.pm
> @@ -3152,7 +3152,16 @@ __PACKAGE__->register_method({
>              syslog('info', "starting qemu termproxy $upid\n");
>  
>              my $cmd =
> -                ['/usr/bin/termproxy', $port, '--path', $authpath, '--perm', 'VM.Console', '--'];
> +                [
> +                    '/usr/bin/termproxy',
> +                    $port,
> +                    '--path',
> +                    $authpath,
> +                    '--perm',
> +                    'VM.Console',
> +                    '--vncticket-endpoint',
> +                    '--',
> +                ];
>              push @$cmd, @$remcmd, @$termcmd;
>  
>              run_command($cmd);

many thanks for your contribution! FYI, the issue was independently
fixed already with commit c9ee34b5 ("api: vnc/termproxy: encode and
verify port in ticket") [0] as part of some other changes, which also
switched to using the 'vncticket' endpoint.

Best Regards,
Fiona

[0]:
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=c9ee34b50280f46b793e93b9652fbbd5a742c6e4




  reply	other threads:[~2026-04-27  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 17:40 [PATCH] fix #6079: use vncticket endpoint for VM serial terminal Koji Nishimura
2026-04-27  9:05 ` Fiona Ebner [this message]
2026-04-27  9:36   ` 西村幸治

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=a8be2fc9-e7d6-4c48-bf3e-84e30d589f29@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=nsm.kkoji@gmail.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal