hardcoresushi
/
libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Update README 

gocryptfs is no longer developed in gocryptfs because of the inconvenience
that you cannot mount a FUSE filesystem inside a FUSE mount
This commit is contained in:
Jakob Unterwurzacher 2015-12-06 15:13:06 +01:00
parent 7375d86ada
commit 21abf57abb
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -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 addition to storing the *master key* in a safe place (the master key is printed
when mounting). 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. Only Linux is supported at the moment. Help wanted for a Mac OS X port.
Testing Testing
@ -100,7 +97,7 @@ The output should look like this:
Changelog Changelog
--------- ---------
v0.5 (in progress) v0.5
* **Stronger filename encryption: DirIV** * **Stronger filename encryption: DirIV**
* Each directory gets a random 128 bit file name IV on creation, * Each directory gets a random 128 bit file name IV on creation,
stored in `gocryptfs.diriv` stored in `gocryptfs.diriv`