Deprecate v0.6 and older filesystems in v1.0 #29
Comments
rfjakob
changed the title
rfjakob
changed the title
|
No objections, assuming that the upgrade path of mounting a newer binary and copying data over still works! 👍 |
|
Upgrade guide added to the wiki: https://github.com/rfjakob/gocryptfs/wiki/Upgrading |
rfjakob
added a commit
that referenced
this issue
Jun 19, 2016
rfjakob
added a commit
that referenced
this issue
Jun 23, 2016
The GCMIV128 feature flag is already mandatory, dropping the command line option is the final step. Completes #29 .
|
v1 has been released, this is done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My current plan is to drop support for filesystems created by gocryptfs v0.6 and older in gocryptfs v1.0. This will get rid of a lot of compatibility code and keep the gocryptfs codebase clean and maintainable. Also, users of
<= v0.6filesystems are missing at least one security improvement (128 bit GCM IVs).I have created a wiki page showing the compatibility matrix: https://github.com/rfjakob/gocryptfs/wiki/Compatibility
Opinions? Disagreement?
The text was updated successfully, but these errors were encountered: