1GIT-SECRET-TELL(1) git-secret 0.3.3 GIT-SECRET-TELL(1)
2
3
4
6 git-secret-tell - adds a person, who can access private data.
7
9 git secret tell [-m] [-d dir] [emails]...
10
12 git-secret-tell receives one or more email addresses as an input,
13 searches for the gpg-key in the gpg homedir by these emails, then
14 imports the corresponding public key into git-secret´s inner keychain.
15 From this moment this person can encrypt new files with the keyring
16 which contains their key, but they cannot decrypt the old files, which
17 were already encrypted without their key. The files should be
18 re-encrypted with the new keyring by someone who has the unencrypted
19 files.
20
21 Versions of git-secret tell after 0.3.2 will warn about keys that are
22 expired, revoked, or otherwise invalid, and also if multiple keys are
23 found for a single email address.
24
25 Do not manually import secret keys into git-secret. It won´t work with
26 imported secret keys anyway.
27
29 -m - takes your current `git config user.email` as an identifier for the key.
30 -d - specifies `--homedir` option for the `gpg`, basically use this option if your store your keys in a custom location.
31 -h - shows help.
32
34 Run man git-secret-tell to see this note.
35
37 git-secret-init(1) http://git-secret.io/git-secret-init,
38 git-secret-add(1) http://git-secret.io/git-secret-add,
39 git-secret-hide(1) http://git-secret.io/git-secret-hide,
40 git-secret-reveal(1) http://git-secret.io/git-secret-reveal,
41 git-secret-cat(1) http://git-secret.io/git-secret-cat,
42 git-secret-killperson(1) http://git-secret.io/git-secret-killperson
43
44
45
46sobolevn November 2020 GIT-SECRET-TELL(1)