RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

From a security pov copy and paste between the guest and the client is not always desirable. So we need to be able to enable/disable this. The best place to do this from an administration pov is on the hypervisor, and thus in the spice-server.

This is implemented by these 2 upstream commits:
http://cgit.freedesktop.org/spice/spice/commit/?id=c2db6d1066bcb73c5ddf9e38c4ef30545706eae9
http://cgit.freedesktop.org/spice/spice/commit/?id=bcf9a60aa97419e12dc83916719e3633bfbb872f

Which are also present on the 0.8 branch, moving to post.

How is this being implemented?  Will there be an option for qemu-kvm?  If so, what would that be and how do we use it?  If this is already documented somewhere just point me to that.

Hi,

(In reply to comment #3)
> How is this being implemented?  Will there be an option for qemu-kvm?

Yes

> If so, what would that be and how do we use it?

It will be an additional option to the -spice cmdline option, called
"disable-copy-paste"

So if for example you normally pass the following spice options:
qemu -spice port=5932,disable-ticketing

You would use the following to disable copy paste:
qemu -spice port=5932,disable-ticketing,disable-copy-paste

Also see bug 693645.

Regards,

Hans

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1634.html