moss

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit dc4fc985f45d133c88d032520c0cf5f9a4f6ae42
parent 6690cd6c246a1377c2d72c6bfcceaa4a65219c54
Author: Daniel Barlow <dan@telent.net>
Date:   Wed, 11 Aug 2021 10:06:56 +0100

add to do

Diffstat:
MREADME.md | 10++++++----
1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md @@ -24,12 +24,12 @@ moss needs you to create an age identity that it will use to decrypt your secrets. You can choose to protect this key with a passphrase, if you have age 1.0.0-rc3 or later - $ age-keygen | age -p > key.age # password-protected key - $ age-keygen > key.age # key with no password (if you have FDE) + $ age-keygen | age -p > key.age # password-protected key + $ age-keygen > key.age # key with no password (if you have FDE) - $ moss init key.age + $ moss init key.age - $ moss git init # if you want to share it with other machines + $ moss git init # if you want to share it with other machines $ moss git remote add me@githost.example.com:/home/git/passwords ## Storing a secret @@ -115,3 +115,5 @@ only writing this down because I figured out how to * check before overwriting secrets that exist already * support re-encrypting a subtree when recipients change * --help option +* warn or fail if iffy store permissions? +