From: Fiona Ebner <f.ebner@proxmox.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com, m.frank@proxmox.com,
berrange@redhat.com, mcascell@redhat.com, qemu-stable@nongnu.org
Subject: Re: [PATCH v2] ui/clipboard: ensure data is available or request callback is set upon update
Date: Wed, 17 Jan 2024 12:29:47 +0100 [thread overview]
Message-ID: <4d6f1a47-3311-4a44-b47c-19035d6cfee0@proxmox.com> (raw)
In-Reply-To: <CAMxuvayHZiXp=VRm=e=HT8u91p3MTut1KXyWOaooEUv7=wZwFg@mail.gmail.com>
Am 17.01.24 um 12:11 schrieb Marc-André Lureau:
> Hi
>
> On Wed, Jan 17, 2024 at 3:01 PM Fiona Ebner <f.ebner@proxmox.com> wrote:
>>
>> + for (type = 0; type < QEMU_CLIPBOARD_TYPE__COUNT && !missing_data; type++) {
>> + if (!info->types[type].data) {
>> + missing_data = true;
>> + }
>> + }
>> + /*
>> + * If data is missing, the clipboard owner's 'request' callback needs to be
>> + * set. Otherwise, there is no way to get the clipboard data and
>> + * qemu_clipboard_request() cannot be called.
>> + */
>> + if (missing_data && info->owner && !info->owner->request) {
>> + return;
>> + }
>
> It needs to check whether the type is "available". If not data is
> provided, owner should be set as well, it should assert() that.
>
> That should do the job:
>
> for (type = 0; type < QEMU_CLIPBOARD_TYPE__COUNT; type++) {
> /*
> * If data is missing, the clipboard owner's 'request' callback needs to
> * be set. Otherwise, there is no way to get the clipboard data and
> * qemu_clipboard_request() cannot be called.
> */
> if (info->types[type].available && !info->types[type].data) {
> assert(info->owner && info->owner->request);
> }
> }
>
Okay, thanks! But we can't assert, because that doesn't resolve the CVE
as it would still crash. The VNC client might not have the
VNC_FEATURE_CLIPBOARD_EXT feature, and the request callback is currently
only set in that case. But we can return instead of assert to just avoid
clipboard update. I'll send a v3.
Best Regards,
Fiona
next prev parent reply other threads:[~2024-01-17 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 11:01 [PATCH v2] ui/clipboard: ensure data is available or request callback is set upon update Fiona Ebner
2024-01-17 11:11 ` Marc-André Lureau
2024-01-17 11:29 ` Fiona Ebner [this message]
2024-01-17 11:33 ` Marc-André Lureau
2024-01-17 11:56 ` Fiona Ebner
2024-01-17 12:20 ` Marc-André Lureau
2024-01-17 14:40 ` Fiona Ebner
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=4d6f1a47-3311-4a44-b47c-19035d6cfee0@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=m.frank@proxmox.com \
--cc=marcandre.lureau@redhat.com \
--cc=mcascell@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).