diff options
| author | rfjakob | 2016-10-25 18:04:29 +0200 |
|---|---|---|
| committer | rfjakob | 2016-10-25 18:04:29 +0200 |
| commit | 1aff8f27a966c0268a2608b27f2078898e70ba2a (patch) | |
| tree | 326489c1b8cc5b959971b7c8692fc1257ae21ea1 /Compatibility.md | |
| parent | 1609e8650ad359ffd28e9b2aec6ecc6033fec493 (diff) | |
Updated Compatibility (markdown)
Diffstat (limited to 'Compatibility.md')
| -rw-r--r-- | Compatibility.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Compatibility.md b/Compatibility.md index 2a742d3..589f063 100644 --- a/Compatibility.md +++ b/Compatibility.md @@ -2,7 +2,7 @@ gocryptfs uses ext4-style *feature flags* to add new functionality or better security to the on-disk-format. These are stored in `gocryptfs.conf` as `FeatureFlags`. When a new feature flag is added, gocryptfs will continue to support mounting older filesystems that do not have this flag set. -However, from time to time major gocryptfs revisions will drop support for very old filesystems. This keeps the gocryptfs code base clean and maintainable. Users are encouraged to upgrade their filesystems (see below for how) as the new features often improve security. If this is not an option, they can stay on the `v0.x` branch which will continue to be supported for bug fixes. +However, from time to time major gocryptfs revisions will drop support for very old filesystems. This keeps the gocryptfs code base clean and maintainable. Users are encouraged to upgrade their filesystems (see below for how) as the new features often improve security. As seen on the table below, v1.0 will be the first version to drop support for very old filesystems (v0.6 and lower). |