From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, berrange@redhat.com
Subject: Re: [virtio-dev] Re: virtio-input for copy/paste?
Date: Wed, 19 Aug 2020 16:35:28 +0100 [thread overview]
Message-ID: <20200819153528.GA2980@work-vm> (raw)
In-Reply-To: <20200817051547.3cnv5jdrwcfr3xwe@sirius.home.kraxel.org>
* Gerd Hoffmann (kraxel@redhat.com) wrote:
> On Mon, Aug 10, 2020 at 05:41:13PM +0100, Dr. David Alan Gilbert wrote:
> > Hi,
> > Is there anywhere that virtio has where host/guest copy/paste would
> > fit?
>
> Well, spice supports it, with spice client and spice guest agent talking
> to each other using a virtio-serial channel (guest <-> spice-server) and
> a spice protocol tunnel (spice-server <-> spice-client).
Right; what I was interested in was whether there would be a way to
plumb copy/paste through for a VNC or local Gtk display; the guest view
should be independent of the transport protocol.
Perhaps that way is just to standardise on the virtio-serial channel
that spice already uses and provide that for other transports;
but if not then it feels like there should be some standard.
> You'll need a guest agent anyway, to bridge between window system
> (x11/wayland/...) and device, so running some protocol over a stream
> doesn't look bad to me as design choice. These days you might choose
> vsock instead (depends on how you design the host side though).
>
> You also need the agent as user interface, so the user can explicitly
> enable clipboard access for the other side (you don't want do this
> automatically for security reasons: the guest should not be able to
> sniff the passwords which you cut+paste on the host from password
> manager to browser).
That should be on the host side-UI shouldn't it?
> > I don't think it's something we have defined at the moment
> > and I was wondering if virtio-input would be the right place to add it.
> > If the client driver supported the feature then the host would
> > hand it to the client, if it didn't it could insert a string
> > of key events.
>
> The problem with such a fallback is keyboard maps. virtio-input sends
> scancodes not keysyms. Even with us-ascii this is a problem (querty vs.
> quertz), and it doesn't become easier with € æ ä ß and emoji ...
Yeh tricky.
Dave
> take care,
> Gerd
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-08-19 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 16:41 [virtio-dev] virtio-input for copy/paste? Dr. David Alan Gilbert
2020-08-17 5:15 ` [virtio-dev] " Gerd Hoffmann
2020-08-19 15:35 ` Dr. David Alan Gilbert [this message]
2020-08-20 5:32 ` Gerd Hoffmann
2020-08-20 7:50 ` Dr. David Alan Gilbert
2020-08-20 8:22 ` Gerd Hoffmann
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=20200819153528.GA2980@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=virtio-dev@lists.oasis-open.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 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.