aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakob Unterwurzacher2021-09-10 12:17:22 +0200
committerJakob Unterwurzacher2021-09-10 12:17:22 +0200
commita85e39f68288af3b9238f7caeefe6eb420b44f02 (patch)
treea47c19d556c0a1b40186e4a39c0eaa10b0679f7f
parentd023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a (diff)
Update README & MANPAGE
-rw-r--r--Documentation/MANPAGE.md4
-rw-r--r--README.md5
2 files changed, 6 insertions, 3 deletions
diff --git a/Documentation/MANPAGE.md b/Documentation/MANPAGE.md
index e4e8f2e..01e4b5a 100644
--- a/Documentation/MANPAGE.md
+++ b/Documentation/MANPAGE.md
@@ -256,9 +256,11 @@ of a case where this may be useful is a situation where content is stored on a
filesystem that doesn't properly support UNIX ownership and permissions.
#### -forcedecode
-
Obsolete and ignored on gocryptfs v2.2 and later.
+See https://github.com/rfjakob/gocryptfs/commit/d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a
+for what it was and why it was dropped.
+
#### -fsname string
Override the filesystem name (first column in df -T). Can also be
passed as "-o fsname=" and is equivalent to libfuse's option of the
diff --git a/README.md b/README.md
index e1104b8..0926095 100644
--- a/README.md
+++ b/README.md
@@ -200,8 +200,8 @@ v2.2, IN PROGRESS
([#151](https://github.com/rfjakob/gocryptfs/issues/151), [#402](https://github.com/rfjakob/gocryptfs/issues/402), [#592](https://github.com/rfjakob/gocryptfs/pull/592))
* New feature flag! You need gocryptfs v2.2 or higher to mount a filesystem that uses this flag.
* `-xchacha`: new option for `-init` (forward mode only). Selects XChaCha20-Poly1305 for content encryption.
- Gives [better performance on embedded CPUs](https://gist.github.com/rfjakob/b28383f4c84263ac7c5388ccc262e38b)
- ([#452](https://github.com/rfjakob/gocryptfs/issues/452))
+ Gives *much* better performance on CPUs without AES acceleration
+ ([#452](https://github.com/rfjakob/gocryptfs/issues/452)).
* New feature flag! You need gocryptfs v2.2 or higher to mount a filesystem that uses this flag.
* Test with `gocryptfs -speed` what is fastest for your CPU, or read [here](https://github.com/rfjakob/gocryptfs/issues/452#issuecomment-908559414)
* `-serialize_reads`: get rid of delay logic by taking advantage of the kernel flag
@@ -209,6 +209,7 @@ v2.2, IN PROGRESS
([go-fuse commit](https://github.com/hanwen/go-fuse/commit/15a8bb029a4e1a51e10043c370970596b1fbb737),
[gocryptfs commit](https://github.com/rfjakob/gocryptfs/commit/a99051b32452c9a781efe248c0014b65d4abddf7))
* Make obsolete `-devrandom` flag a no-op ([commit](https://github.com/rfjakob/gocryptfs/commit/61ef6b00a675456ee05d40f1ce44d693bc4be350))
+* Make `-forcedecode` flag a no-op ([commit](https://github.com/rfjakob/gocryptfs/commit/d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a))
v2.1, 2021-08-18
* `-fido2`: do not request PIN on `gocryptfs -init` fixing `FIDO_ERR_UNSUPPORTED_OPTION` with YubiKey