README: rewording
This commit is contained in:
parent
cd4aa22291
commit
80689c627e
1 changed files with 8 additions and 4 deletions
12
README.md
12
README.md
|
@ -1,6 +1,7 @@
|
||||||
# GPGTool
|
# GPGTool
|
||||||
|
|
||||||
Zsh script to manage GPG keys without storing the master key.
|
Zsh script to manage GPG keys without storing the master key in your main GnuPG
|
||||||
|
keyirng.
|
||||||
|
|
||||||
**This is currently in a *TESTING* state. Do not use for production unless you
|
**This is currently in a *TESTING* state. Do not use for production unless you
|
||||||
can manually verify each step doesn’t accidentally leak into your main GnuPG
|
can manually verify each step doesn’t accidentally leak into your main GnuPG
|
||||||
|
@ -14,9 +15,12 @@ keys.
|
||||||
An attacker will be able to use the currently valid sub keys until you revoke
|
An attacker will be able to use the currently valid sub keys until you revoke
|
||||||
them. They will _never_ be able to create new sub keys for your master key.
|
them. They will _never_ be able to create new sub keys for your master key.
|
||||||
|
|
||||||
So in case of compromise of your GPG key(s), whip out your securely stored
|
So in case of compromise of your GPG key(s)
|
||||||
master key, invalidate your current sub keys, make sure to propagate that e.g.
|
|
||||||
via key server and generate new sub keys.
|
1. whip out your securely stored master key,
|
||||||
|
2. revoke your current sub keys,
|
||||||
|
3. make sure to propagate that e.g. via key server and
|
||||||
|
4. generate new sub keys.
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue