Right now a Kin project consists of two simple folders, a private and public folder. These folders then get packaged up during the compile process. For privacy and security, this scheme means:
It's a really good idea to make sure your project is in a location on your file system where hard drive encryption is enabled, to avoid writing private data to your disk where it can be recovered by someone else.
You have to take special care to disable things like search indexing for the private folder, etc. if your operating system or other software automatically does that for you.
If you ever want to put your work away for now and come back to it later, you'll probably want to encrypt your project manually using some other software (like GPG) and decrypt it when you're ready to come back to it again.
Remember, we're putting our most sensitive information in this backup project. This is not just a hassle; it's also too easy to make mistakes.
Instead of relying on the OS file system, look into using Zbox to store all our private files, config files, etc. A private, exclusive, encrypted file system would protect us from all the scenarios above.
Advantages:
It's easier / safer to keep an ongoing project that can be frequently updated.
Even if the password protecting the Zbox file system were a default hard-coded value, or "1234," it would still go a long way toward protecting us from data leaks.
We don't need to zip everything up in a compressed archive before encrypting; we can just encrypt / copy the Zbox file system itself to the destination backup during the compile step.
Disadvantages:
Rather than using a file browser to drag / drop files into our project, we'll need commands to manage files in the project. Something like this, perhaps:
kin file add ~/super/secret/info.txt
kin file rm old_info.txt
kin file list
Etc. These commands would be the only way to interact with your private data.
Users will have to remember a password to manage their backup project.
This may also warrant creating a background process, similar to a GPG or SSH "agent" process that remembers our Zbox encryption password for a limited time, so we don't require users to type in their password every time they do something in the project.
Right now a Kin project consists of two simple folders, a private and public folder. These folders then get packaged up during the compile process. For privacy and security, this scheme means:
Remember, we're putting our most sensitive information in this backup project. This is not just a hassle; it's also too easy to make mistakes.
Instead of relying on the OS file system, look into using Zbox to store all our private files, config files, etc. A private, exclusive, encrypted file system would protect us from all the scenarios above.
Advantages:
Disadvantages:
Etc. These commands would be the only way to interact with your private data.
This may also warrant creating a background process, similar to a GPG or SSH "agent" process that remembers our Zbox encryption password for a limited time, so we don't require users to type in their password every time they do something in the project.