https://bugs.kde.org/show_bug.cgi?id=436738

David Hurka <david.hu...@mailbox.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=317856

--- Comment #10 from David Hurka <david.hu...@mailbox.org> ---
In Bug 317856, it was requested to store the file name only as a hash.

Related, in the merge request
https://invent.kde.org/graphics/okular/-/merge_requests/422#note_238154 (Create
“Welcome screen” that replaces window where nearly all widgets are in disabled
state) Jiří Wolker writes:

> And there is also privacy risk – users sometimes do not want to store
> thumbnails of their documents. (Example: Home directory incl. config
> files is not encrypted, Documents is. When user opens file from Documents,
> the thumbnail gets stored in the home directory. This makes unencrypted
> image of part of the file.)

My idea would be to store docdata (maybe including thumbnails) hashed by the
file name/path/content, and encrypted with a hash of the file content, so they
can only be read with read access to the document file (or a copy of it).

To delete old docdata files, there could be a list of the last 5000 used
docdata files. This list is updated every time a file is opened/closed, and
those docdata not anymore in the list are deleted. Those docdata which are so
old that they leave the “Open Recent” list, are stripped from their thumbnail.

But this way, there wouldn’t be a reliable way to detect duplicate docdata
files.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to