Red Hat Bugzilla – Bug 963055
"vncviewer --AcceptClipboard=0" accepts clipboard updates
Last modified: 2013-07-27 21:05:16 EDT
Description of problem:
The viewer accepts clipboard updates from the server even when --AcceptClipboard=0 is passed on the command line.
I want to be able to copy and paste between local applications while a VNC session to an untrusted account is running without risk of the VNC session overwriting my local clipboard with harmful content without notice. To do so, I need to configure the viewer not to accept clipboard updates. (I have a separate script to copy data between the local and remote clipboards when I request it.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. vncserver :2 (or some available display number)
2. vncviewer --AcceptClipboard=0 :2
3. In the VNC session, copy something to the clipboard.
4. Go to a window outside the VNC session and paste.
The content from the VNC session is pasted.
The content previously on the local clipboard, if any, is pasted.
Created attachment 748055 [details]
I rebuilt the tigervnc RPMs with the attached patch and it seems to fix the problem.
It looks like the conditional on acceptClipboard was lost in the move to the "new FLTK viewer" (upstream SVN r4345). Ideally I would take this bug upstream; we'll see if I get around to it.
Thanks for spotting this. Will be in the next upstream release. :)
Should be fixed in tigervnc-1.3.0-1.fc19.
tigervnc-1.3.0-1.fc19 has been submitted as an update for Fedora 19.
tigervnc-1.3.0-3.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tigervnc-1.3.0-3.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
tigervnc-1.3.0-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.