-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a warning about the inter-qube clipboard maximum character limit #9296
Add a warning about the inter-qube clipboard maximum character limit #9296
Comments
I offer that the warning also suggest the user instead copy files between qubes. Not that it will present a popup, but rather say the likes of "you can use use qvm-copy to copy large files between qubes." |
@marmarek I am looking at commit history to |
Thanks for the hint. Regardless of the OP, 65KB sound a little bit low (maybe even 12 years ago). This is less than 1000 at 40 chars width. Was there any security concern? |
After some consideration and study about this issue, it is not be simple. I could divide it to 4 (+1) individual sub-tasks:
|
For the task 2 & 3, instead of truncation which might result in data loss and corruption, a proper message could be raised as suggested above. But why not a popup? It could be a popup with this text:
|
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. Supplements: QubesOS/qubes-issues#9296
Also making the clipboard buffer size to be user configurable on the GUI daemon side (xside). Supplements: QubesOS/qubes-issues#9296
Also making the clipboard buffer size to be user configurable on the GUI daemon side (xside). Supplements: QubesOS/qubes-issues#9296
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. Supplements: QubesOS/qubes-issues#9296
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. Supplements: QubesOS/qubes-issues#9296
Also making the clipboard buffer size to be user configurable on the GUI daemon side (xside). Supplements: QubesOS/qubes-issues#9296
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. Supplements: QubesOS/qubes-issues#9296
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. fixes: QubesOS/qubes-issues#9296
Check if copying 64k also works. And then try copying 200kb, both with default settings (should be refused) and with limit raised. This test assume already modified behavior on over the limit copy (truncate to 0 instead of truncating to the limit). Finally, test copying 300k, which should be rejected regardless of the limit. QubesOS/qubes-issues#9296
Users will be able to set global and/or per qube clipboard limit size by setting `max_clipboard_size` feature of GUIVM or individual qubes Clipboard sizes over the limit will trigger special event for a pop-up fixes: QubesOS/qubes-issues#9296
Users will be able to set global and/or per qube clipboard limit size by setting `max_clipboard_size` feature of GUIVM or individual qubes Clipboard sizes over the limit will trigger special event for a pop-up fixes: QubesOS/qubes-issues#9296
Users will be able to set global and/or per qube clipboard limit size by setting `max_clipboard_size` feature of GUIVM or individual qubes Clipboard sizes over the limit will trigger special event for a pop-up fixes: QubesOS/qubes-issues#9296
Users will be able to set global and/or per qube clipboard limit size by setting `max_clipboard_size` feature of GUIVM or individual qubes Clipboard sizes over the limit will trigger special event for a pop-up fixes: QubesOS/qubes-issues#9296
Improving clipboard message using the new GUI protocol 1.8 fixes: QubesOS/qubes-issues#9296
Check if copying 64k also works. And then try copying 200kb, both with default settings (should be refused) and with limit raised. This test assume already modified behavior on over the limit copy (truncate to 0 instead of truncating to the limit). Finally, test copying 300k, which should be rejected regardless of the limit. QubesOS/qubes-issues#9296
Check if copying 64k also works. And then try copying 200kb, both with default settings (should be refused) and with limit raised. This test assume already modified behavior on over the limit copy (truncate to 0 instead of truncating to the limit). Finally, test copying 300k, which should be rejected regardless of the limit. Change also `zenity --entry` to `zenify --text-info --editable` as the former supports only up to 65535 characters. QubesOS/qubes-issues#9296
If vmside clipboard is over the maximum limit, sending one byte over maximum limit should trigger inter-vm clipboard rejection instead of truncation. If vmside clipboard is over 256KiB (X11 INCR), send a warning message fixes: QubesOS/qubes-issues#9296 fixes: QubesOS/qubes-issues#5220
Check if copying 64k also works. And then try copying 200kb, both with default settings (should be refused) and with limit raised. This test assume already modified behavior on over the limit copy (truncate to 0 instead of truncating to the limit). Finally, test copying 300k, which should be rejected regardless of the limit. Change also `zenity --entry` to `zenify --text-info --editable` as the former supports only up to 65535 characters. QubesOS/qubes-issues#9296
Improving clipboard message using the new GUI protocol 1.8 fixes: QubesOS/qubes-issues#9296
Necessary for 1.8 protocol definition (with increased max clippboard size). QubesOS/qubes-issues#9296
Necessary for 1.8 protocol definition (with increased max clippboard size). QubesOS/qubes-issues#9296
A brief note to potential 1st time contributors who are looking at historic issues with good first issue Label and wondering why the approved solution is relatively complex. The simple solution to this issue could had been a simple patch to |
Check if copying 64k also works. And then try copying 200kb, both with default settings (should be refused) and with limit raised. This test assume already modified behavior on over the limit copy (truncate to 0 instead of truncating to the limit). Finally, test copying 300k, which should be rejected regardless of the limit. Change also `zenity --entry` to `zenify --text-info --editable` as the former supports only up to 65535 characters. QubesOS/qubes-issues#9296
The problem you're addressing (if any)
The inter-qube clipboard system appears to have a 65000 character limit, which means that any text longer than this limit that is copied between individual qubes by using the ctrl+shift+c and ctrl+shift+v shortcuts will be silently truncated to 65000 characters. I noticed this in Q4.2 while trying to copy over some config files from one GUI text editor to another in a different qube, and then some syntax errors appeared in the program log. Upon inspection, I noticed that a portion of the config file in the new qube was missing.
The solution you'd like
Please add some sort of warning message on the screen. When a user tries to copy a text section that is longer than this limit then a message should pop up notifying the user that not all text has been copied over.
The value to a user, and who that user might be
Any user who copies large portions of text won't wonder why some of it has disappeared.
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)
The text was updated successfully, but these errors were encountered: