https://bugs.kde.org/show_bug.cgi?id=372116
--- Comment #53 from pallaswept <pallasw...@proton.me> ---
(In reply to Shmerl from comment #52)
> There is no reason why this can't be added in stages, first copy and then
> paste with security controls for it. So it's not a a blocker not to merge
> current accumulated progress.
Oh of course, it is not my intention here to block anything! To the contrary.
I'm not trying to prevent anyone from adding copy. I'm trying to prevent delays
in adding paste, from placing security above accessibility - There's no point
having a totally secure device that you can't use. That's called a rock :D
Looking at other terminals which have implemented this and which also paused on
adding paste because security, they've all done the same thing in essence - had
a box to tick, which enables the feature. There's no granular, per-process
security ('X can paste, Y can't') or anything like that, and it seems no such
mechanism really exists anyway, so there's just an on/off switch that defaults
to off. I don't suppose something like that should hold things up too much?
Honestly, I imagine that a programmer who knows KDE well could probably add
said tickbox in a few minutes. But I don't know what I'm talking about, I could
be wrong.
Realistically, people who *need* the feature, aren't going to complain too
loudly if it's missing a GUI and requires them to edit configs directly or
something (kwriteconfig?) - so that might help find a solution without loading
a dev and without a long delay? ... Just trying to think of ways to make it
quick (for the users), and easy (for the devs).
--
You are receiving this mail because:
You are watching all bug changes.
