https://bugs.kde.org/show_bug.cgi?id=274102
Marcell Fulop <marek...@protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marek...@protonmail.com
--- Comment #10 from Marcell Fulop <marek...@protonmail.com> ---
Hey, why was this reopened a few days ago after so long?...
---
I think it's a very valid feature request, but it's controversial. It's the Mac
philosophy where TextEdit stores unsaved docs in the cloud encrypted by
default, or if that's prevented, locally. But in Mac (or iOS for that matter),
every app is in its isolated container so privacy is not as much of a concern.
On the other hand, not sure if you noticed, privacy war has exploded. It's a
big question nowadays if and who is willing to store sensitive data with big IT
firms, or leave it unencrypted on a disk. Sure, not all data is sensitive, but
a permanent feature like this would compromise the potentially sensitive
unsaved documents.
File system permission could provide somewhat sufficient measures to prevent
unauthorised access but may not be enough. The point is that many wouldn't be
convinced that their unsaved files will _always_ be stored say in their home
dir is good at all.
So, in my opinion, a solution that's elegant and also acceptable by today's
measures would be something along these lines:
When content is added for the first time to a new, unsaved doc, Kate offers a
dialog, asking if the user wishes to be able to restore the unsaved document.
The actions are 'Yes' and 'No' with a checkbox 'Remember my decision'.
When 'Remember my decision' is not set, Kate always asks.
When 'Yes' is selected, Kate informs that it will be stored unencrypted. (...
or the possibilities from here are many. E.g. offers to store with symmetric
encryption with a unique key per doc, or, with one key globally for all unsaved
documents, or offers to select a PGP key to encrypt with, etc...)
--
You are receiving this mail because:
You are watching all bug changes.
