diff options
| author | Jakob Unterwurzacher | 2015-12-06 15:13:06 +0100 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2015-12-06 15:13:06 +0100 |
| commit | 21abf57abbfc6ad818df623f007cac1aa1945682 (patch) | |
| tree | 810b074332a51f73b82f7b5b5895e45eb3010f11 | |
| parent | 7375d86adae6f9ddcb403c67c5a97ed917b2ae3f (diff) | |
Update READMEv0.5.1
gocryptfs is no longer developed in gocryptfs because of the inconvenience
that you cannot mount a FUSE filesystem inside a FUSE mount
| -rw-r--r-- | README.md | 5 |
1 files changed, 1 insertions, 4 deletions
@@ -18,9 +18,6 @@ Beta. You are advised to keep a backup of your data outside of gocryptfs, in addition to storing the *master key* in a safe place (the master key is printed when mounting). -That said, I am dogfooding on gocryptfs for some time now. In fact, all gocryptfs -development happens inside a mounted gocryptfs filesystem, with no issues so far. - Only Linux is supported at the moment. Help wanted for a Mac OS X port. Testing @@ -100,7 +97,7 @@ The output should look like this: Changelog --------- -v0.5 (in progress) +v0.5 * **Stronger filename encryption: DirIV** * Each directory gets a random 128 bit file name IV on creation, stored in `gocryptfs.diriv` |