From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-dev-return-7687-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id A1C0E985D39 for ; Wed, 19 Aug 2020 15:35:39 +0000 (UTC) Date: Wed, 19 Aug 2020 16:35:28 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20200819153528.GA2980@work-vm> References: <20200810164113.GH3052@work-vm> <20200817051547.3cnv5jdrwcfr3xwe@sirius.home.kraxel.org> MIME-Version: 1.0 In-Reply-To: <20200817051547.3cnv5jdrwcfr3xwe@sirius.home.kraxel.org> Subject: Re: [virtio-dev] Re: virtio-input for copy/paste? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline To: Gerd Hoffmann Cc: virtio-dev@lists.oasis-open.org, berrange@redhat.com List-ID: * 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? >=20 > 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). >=20 > 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. >=20 > 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 =E2=82=AC =C3=A6 =C3=A4 =C3=9F= and emoji ... Yeh tricky. Dave > take care, > Gerd >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org >=20 --=20 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