https://bugs.kde.org/show_bug.cgi?id=372116
un...@mail.ru changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |un...@mail.ru
--- Comment #5 from un...@mail.ru ---
There is another solution for remote clipboard support in terminal, already
working in real life: the file manager far2l (a fork of Far Manager 2 ported to
Linux/BSD/Mac) has a built-in virtual terminal emulator that supports so-called
"far2l extensions", including access to the local clipboard.
The security problem is solved there as follows: when accessing the clipboard
for the first time, terminal displays a message to the user, offering to choose
from the following options: "block current attempt to access local clipboard",
"do not try to access local clipboard at all", "allow local clipboard access"
and "always allow local clipboard access". In the latter case, a random
identifier is generated on the remote server, which is memorized by the
terminal and used later to authorize access to the clipboard. Of course, this
identifier can be leaked, since it is stored unencrypted on server side, so the
last option is recommended for use only on servers completely controlled by the
user.
Just the same logic may be applied then implementing OSC 52 support.
Further reading:
https://github.com/elfmz/far2l
https://github.com/elfmz/far2l/blob/master/far2l/bootstrap/scripts/FarEng.hlf.m4#L1293
https://github.com/elfmz/far2l/blob/master/far2l/VTFar2lExtensios.cpp#L17
--
You are receiving this mail because:
You are watching all bug changes.
