fscrypt.git/cmd/fscrypt/strings.go, branch v0.3.2 Go tool for managing Linux filesystem encryption README: write "Linux native filesystem encryption" 2021-12-22T00:03:08+00:00 Eric Biggers ebiggers@google.com 2021-12-22T00:03:08+00:00 d6638ac45f6b6da373f7f724251aef03032915ad "Linux filesystem encryption" sounds too vague. Write "Linux native filesystem encryption" instead. 
"Linux filesystem encryption" sounds too vague.  Write "Linux native
filesystem encryption" instead.
cmd: Simplify "fscrypt --version" output (#207) 2020-03-23T21:24:48+00:00 Joseph Richey joerichey@google.com 2020-03-23T21:24:48+00:00 f10aadb2675b26d351365c6c208c930b6d4c619c There's no need to include the build time, author, and copyright info in the output of "fscrypt --version". This information is: - Overly complex (the current string is hard to parse) - Inaccurate (there are other authors than just me) - Unnecessary (the Apache 2 license is for Source Code) - Makes reproducible builds impossible The default version string is just fine. Signed-off-by: Joe Richey <joerichey@google.com> 
There's no need to include the build time, author, and copyright info
in the output of "fscrypt --version". This information is:

  - Overly complex (the current string is hard to parse)
  - Inaccurate (there are other authors than just me)
  - Unnecessary (the Apache 2 license is for Source Code)
  - Makes reproducible builds impossible

The default version string is just fine.

Signed-off-by: Joe Richey <joerichey@google.com>
 Fix various typos and grammatical errors (#141) 2019-09-09T02:46:59+00:00 ebiggers ebiggers@google.com 2019-09-09T02:46:59+00:00 6445dad7d66fa6a1867090fcd9602c98863649f6 These were found by a combination of manual review and a custom script that checks for common errors. Also removed an outdated sentence from the comment for setupBefore(). 
These were found by a combination of manual review and a custom script
that checks for common errors.

Also removed an outdated sentence from the comment for setupBefore().
 cmd/fscrypt: don't show build time if not set 2018-02-12T07:38:19+00:00 Joseph Richey joerichey94@gmail.com 2018-02-12T07:38:19+00:00 1f508cc30f3c1caadea5c648158880eacfe9b113 






cmd/fscrypt: more nits to fix "make lint"
2017-07-18T06:20:51+00:00

Joe Richey joerichey@google.com
joerichey@google.com

2017-07-18T06:18:49+00:00

e4cb9c6cef2d75cdc5ca62777d2fa0e44f813fd4












cmd/fscrypt: setup, encrypt, unlock commands
2017-06-28T22:15:21+00:00

Joe Richey joerichey@google.com
joerichey@google.com

2017-06-21T17:21:21+00:00

37c866e1e16a6d2dded11ba93c2e04af3764a139

This commit adds in the framework for adding commands and subcommands to
the fscrypt tool. This commit adds in the "setup", "encrypt", and
"unlock" commands. Additional information can be found by running:
    fscrypt <command> --help.

This commit defines how flags are parsed and errors are handled. It also
creates an extensible framework for prompting the user for information.

Change-Id: I159d7f44ee2b2bbc5e072f0802850e082d9a13ce





This commit adds in the framework for adding commands and subcommands to
the fscrypt tool. This commit adds in the "setup", "encrypt", and
"unlock" commands. Additional information can be found by running:
    fscrypt <command> --help.

This commit defines how flags are parsed and errors are handled. It also
creates an extensible framework for prompting the user for information.

Change-Id: I159d7f44ee2b2bbc5e072f0802850e082d9a13ce