Set up your own truly secure, encrypted and shared file synchronization

Two things:<p>1. You have been able to use rsync.net as a target for this scheme for ... 4-5 years now. [1]<p>2. <a href="https://news.ycombinator.com/item?id=5640700" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=5640700</a><p><pre><code> [1] ssh user@rsync.net &quot;git init --bare autosync.git&quot; Initialized empty Git repository in &#x2F;user&#x2F;autosync.git&#x2F;</code></pre>

This encrypts via encfs, so not sure what the advantage is over just using encfs on top of Dropbox (or any ol&#x27; provider)?

I&#x27;ve been using Sparkleshare (<a href="http://sparkleshare.org/" rel="nofollow">http:&#x2F;&#x2F;sparkleshare.org&#x2F;</a>) as a secure alternative to Dropbox, and it works decently, although it has some rough edges.

Why does including the EncFS XML file make things much easier to crack?

I like that dvcs-autosync is able to keep a history, but I wouldn&#x27;t use it because it doesn&#x27;t have the ability to delete old versions of a file yet.

Duplicity [1] is a good alternative too.<p>[1] <a href="http://duplicity.nongnu.org/" rel="nofollow">http:&#x2F;&#x2F;duplicity.nongnu.org&#x2F;</a>