diff options
author | Jakob Unterwurzacher | 2021-09-10 12:14:19 +0200 |
---|---|---|
committer | Jakob Unterwurzacher | 2021-09-10 12:14:19 +0200 |
commit | d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a (patch) | |
tree | 8e5df3a175b183f0db989a9d8f940a3c5c7434b0 /Documentation | |
parent | c974116322f057a36ffb0b2ec0338b7f60872773 (diff) |
cli: drop -forcedecode flag
The rewritten openssl backend does not support this flag anymore,
and it was inherently dangerour. Drop it (ignored for compatibility)
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/MANPAGE.md | 15 |
1 files changed, 1 insertions, 14 deletions
diff --git a/Documentation/MANPAGE.md b/Documentation/MANPAGE.md index 7371fc2..e4e8f2e 100644 --- a/Documentation/MANPAGE.md +++ b/Documentation/MANPAGE.md @@ -256,21 +256,8 @@ 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 -Force decode of encrypted files even if the integrity check fails, instead of -failing with an IO error. Warning messages are still printed to syslog if corrupted -files are encountered. -It can be useful to recover files from disks with bad sectors or other corrupted -media. It shall not be used if the origin of corruption is unknown, specially -if you want to run executable files. -For corrupted media, note that you probably want to use dd_rescue(1) -instead, which will recover all but the corrupted 4kB block. - -This option makes no sense in reverse mode. It requires gocryptfs to be compiled with openssl -support and implies -openssl true. Because of this, it is not compatible with -aessiv, -that uses built-in Go crypto. - -Setting this option forces the filesystem to read-only and noexec. +Obsolete and ignored on gocryptfs v2.2 and later. #### -fsname string Override the filesystem name (first column in df -T). Can also be |