https://bugs.kde.org/show_bug.cgi?id=410457
Ivan Čukić <ivan.cu...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INTENTIONAL
--- Comment #4 from Ivan Čukić <ivan.cu...@kde.org> ---
To repeat, if you want encryption just for the cloud sync, which is unlocked
while you're logged in, Vault is not the solution. It is not Vault's use-case.
Vault is *not* going to support use-cases which blur the best practices for its
use-case.
One of the interesting things I've been researching recently (which might end
up as a new KDE project at one point) is git+gpg which provides a nice
end-to-end encryption. The local files are not encrypted, but they are sent
properly encrypted to a git server. This would be a good tool for your
use-case.
As mentioned before, the alternative is to set up the usual encrypted $HOME (or
some other directory) and sync the encrypted data with your cloud provider.
This would have the benefit of gpg+git with added protection against device
theft if it is stolen while powered off.
P.S. Bug status is meant for developers to classify bugs. While we all
appreciate the discussion, there is no point in reopening a bug unless a
developer reopens it because the discussion made them see the problem in a
different light.
--
You are receiving this mail because:
You are watching all bug changes.
