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

Update README for v1.0

Browse Source
This commit is contained in:
Jakob Unterwurzacher 2016-07-17 12:19:50 +02:00
parent 0a3225b1eb
commit 2e519b9609
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -21,10 +21,14 @@ for details.
Current Status Current Status
-------------- --------------
gocryptfs is a young project. While bugs in any software can cause issues, gocryptfs has reached version 1.0 on Jul 17, 2016. It has gone through
bugs in encryption software can cause catastrophic data loss. Keep a backup hours and hours of stress (fsstress, extractloop.bash) and correctness
of your gocryptfs filesystem *and* store a copy of your master key (printed testing (xfstests). It is now considered ready for general consumption.
on mount) in a safe place. See below for how gocryptfs is tested.
The old principle still applies: Important data should have a backup.
Also, keep a copy of your master key (printed on mount) in a safe place.
This allows you to access the data even if the gocryptfs.conf config
file is damaged or you lose the password.
Platforms Platforms
--------- ---------
@ -111,7 +115,7 @@ RM: 4.42
Changelog Changelog
--------- ---------
v1.0-rc1, 2016-07-06 v1.0, 2016-07-17
* Deprecate very old filesystems, stage 3/3 * Deprecate very old filesystems, stage 3/3
* Filesystems created by v0.6 can no longer be mounted * Filesystems created by v0.6 can no longer be mounted
* Drop command-line options `-gcmiv128`, `-emenames`, `-diriv`. These * Drop command-line options `-gcmiv128`, `-emenames`, `-diriv`. These