diff options
| author | Eric Biggers <ebiggers@google.com> | 2021-09-13 12:40:14 -0700 |
|---|---|---|
| committer | Eric Biggers <ebiggers@google.com> | 2021-09-13 12:40:14 -0700 |
| commit | 8e44543ccb77d2fd4a642d83aa8ef79bf06b4d3f (patch) | |
| tree | c647f4a5846a3d960607e04ce8bf5b10a64a5da2 /README.md | |
| parent | 09371853570b1b9afd75865e3b7125445a44ecd5 (diff) | |
README: remove note about planned commands
These would still be nice to add. However, the mention of them in the
README is misleading because people reading it might come away with the
impression that there is currently no way to back up fscrypt metadata or
to recover directories -- which isn't true. (The fscrypt metadata is
just a directory which can be backed up like any other directory. And
'fscrypt encrypt' already offers to generate a recovery passphrase when
the directory and protector are on different filesystems.)
Just remove this note; it doesn't really add any value.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -139,11 +139,6 @@ Concretely, `fscrypt` contains the following functionality: * `fscrypt status [PATH]` - Gets detailed info about filesystems or paths * `fscrypt metadata` - Manages policies or protectors directly -The following functionality is planned: -* `fscrypt backup` - Manages backups of the `fscrypt` metadata -* `fscrypt recovery` - Manages recovery keys for directories -* `fscrypt cleanup` - Scans filesystem for unused policies/protectors - See the example usage section below or run `fscrypt COMMAND --help` for more information about each of the commands. |