This is part three of a series about encrypted file storage/archive systems. My plan is to try out duplicity, git using transparent encryption, s3-based storage systems, git-annex and encfs+sshfs as alternatives to Dropbox/Wuala/Spideroak. The conclusion will be a blog post containing a comparison a.k.a. “executive summary” of my findings. Stay tuned.
git was originally written by Linus Torvalds as SCM tool for the Linux Kernel. It’s decentralized approach fits well into online OSS projects, it slowly got the decentralized OSS of choice for many. Various dedicated hosted storage services as github or bitbucket arose. In this post I’ll look into using git as replacement for Dropbox for data sharing. As Dropbox has a devastating security history (link needed) I’ll look into ways of transparently encrypting remote git repositories.
If you’re a software developer you might already know git’s basic operations. If not look at [this introduction](). Git is a decentralized version control system: this makes it inherently multi-user. In addition remote servers are mostly treaded as dumb storage dumps without active logic which would fit perfectly our needs.
But what for non tech-savvy users? Fortunately there’s SparkleShare. This user interface works like Dropbox but with a git back-end. I really like that it is using a git repository, through that it doesn’t matter if you trust SparkleShare’s quality: in the end all data is stored within a trusted (safety-wise) git repository. SparkleShare uses an external notification server for notifying the different clients about changed files, really paranoid should create their own notification servers.
Server-wise there are plenty of hosed storage providers like github or bitbucket. Self-hosted solutions range from basic setups over SSH to full-blown github clones like gitlab (including access control, etc.). An advanced feature that I’ve come to love is server-side editing through a HTML editor (similar functionality is provided by githab/bitbucket/gitlab).
Data transfer can be utilized through various protocols, most commonly SSH or HTTPS are used. This provides for secure transport but alas server-side storage is unencrypted.
Adding encryption through SparkleShare
SparkleShare provides easy server-side encryption by just adding “-crypto” to a repository’s name. To create a new repository and access it through SSH do the following on the server (I assume that you’ve copied you SSH public keys to the storage server):
and check it out through SparkleShare:
After entering the repository data Sparkleshare asks for an encryption password. To test it, we’re gonna check out the repository through ‘normal’ git and output one of the stored files:
Encryption looks good (but see that the filename was not encrypted). But how was it done?
Data is passed to the
clean filter before check-ins/check-outs (this is achieved through the filter statement in
.git/info/attributes). This filter in turn use the Password from .git/password to encrypt the user data. What’s bad about it? First of all there’s no key change mechanism: you cannot easily change the encryption password for the repository. Second the password is saved on each SparkleShare client as plain-text and can easily be read by everyone. At least this uses CBC as block cipher, this is a secure default. Fourth and biggest problem is that the filename is not encrypted at all. This means that an attacker can easily see what files you have stored.
on the command line: git-encrypt / git-crypt
Let’s start with git-encrypt: this tool has all the problems of SparkleShare. In addition it uses ECB as cipher mode. This means that the resulting encrypted files are not as useless (without the secret key) as you might hope you would be. Especially for bitmap images this might mean that the encryption is mostly meaningless. You can change the default through the configuration file but I prefer tools with better defaults.
In steps git-crypt. This uses CTR mode as block cipher (with an IV derived from the SHA1 mac of the source file). This produces secure encrypted files (as well as works with git) and should also be parallelizeable on a multi-core/CPU system. The filename is still unencrypted through, also the password can be found in plain-text on the Client’s computer. You cannot easily exchange the encryption password.
on the command line: encrypting with GPG
I also found an article that utilized public-key encryption through gpg for encryption.
This means that the
.git/config entries would look like:
1 2 3
[filter „crypto“] smudge = gpg -d -q –batch –no-tty -r MYKEYID clean = gpg -ea -q –batch -no-tty -r MYKEYID
With this the secret password (to the gpg key) is not stored in plain text. Encryption does not depend upon knowledge of the password, for decryption it must be passed on to gpg (through gpg-agent for example). Alas this should be slower than using plain symmetric encryption (as with openSSL) and the filenames are still stored unencrypted.
Author Andreas Happe
License CC BY-NC-ND 4.0