eafd3fc531
* Migrate docs to master branch, add action to deploy to pages branch on push * Update docs, build pipeline to reflect new method of updating gh-pages * Removed make build-gh-pages from post-commit hook Co-authored-by: Josh Rabinowitz <joshr@joshr.com>
1.8 KiB
| layout | title | date | permalink | categories |
|---|---|---|---|---|
| post | git-secret-tell | 2020-09-20 15:12:56 -0400 | git-secret-tell | command |
git-secret-tell - adds a person, who can access private data.
SYNOPSIS
git secret tell [-m] [-d dir] [emails]...
DESCRIPTION
git-secret-tell receives one or more email addresses as an input, searches for the gpg-key in the gpg
homedir by these emails, then imports the corresponding public key into git-secret's inner keychain.
From this moment this person can encrypt new files with the keyring which contains their key,
but they cannot decrypt the old files, which were already encrypted without their key.
The files should be re-encrypted with the new keyring by someone who has the unencrypted files.
Versions of git-secret tell after 0.3.2 will warn about keys that are expired, revoked, or otherwise invalid,
and also if multiple keys are found for a single email address.
Do not manually import secret keys into git-secret. It won't work with imported secret keys anyway.
OPTIONS
-m - takes your current `git config user.email` as an identifier for the key.
-d - specifies `--homedir` option for the `gpg`, basically use this option if your store your keys in a custom location.
-h - shows help.
MANUAL
Run man git-secret-tell to see this note.
SEE ALSO
git-secret-init(1), git-secret-add(1), git-secret-hide(1), git-secret-reveal(1), git-secret-cat(1), git-secret-killperson(1)