DOC: justify why you would want to sign your new key

This commit is contained in:
Thomas A Caswell 2019-08-26 21:10:19 -04:00
parent 5df1226971
commit f8880975b8
No known key found for this signature in database
GPG Key ID: BCD928050D713D75
1 changed files with 14 additions and 5 deletions

View File

@ -416,16 +416,25 @@ Export the key ID as a [variable](https://stackoverflow.com/questions/1158091/de
$ export KEYID=0xFF3E7D88647EBCDB $ export KEYID=0xFF3E7D88647EBCDB
``` ```
# Sign with an existing key (if you have one) # Sign with an existing key (optional)
Export your existing key to move it to the working keyring. From a different terminal do: If you already have a pgp key you may want want to sign your new key
with the old one to help prove that your new key is infact controlled
by you.
Export your existing key to move it to the working keyring. From a
different terminal do:
```console
$ gpg --export-secret-keys --armor --output /tmp/new.sec $ gpg --export-secret-keys --armor --output /tmp/new.sec
```
and then to export your old key and then
```console
$ gpg --default-key $OLDKEY --sign-key $KEYID $ gpg --default-key $OLDKEY --sign-key $KEYID
```
# Sub-keys # Sub-keys