fix: add an explicit example about publishing the pubkey when expiring

pull/387/head
Dalibor Karlović 2023-06-26 11:19:08 +02:00 committed by GitHub
parent fec6e92b8f
commit 619537629f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 1 deletions

View File

@ -2026,7 +2026,7 @@ Key is valid for? (0)
```
Follow these prompts to set a new expiration date, then `save` to save your changes.
Next, export the public key:
Next, [export the public key](#export-public-keys):
```console
$ gpg --armor --export $KEYID > gpg-$KEYID-$(date +%F).asc
@ -2038,6 +2038,18 @@ Transfer that public key to the computer from which you use your GPG key, and th
$ gpg --import gpg-0x*.asc
```
Alternatively, use a public key server (it will update the key if already on the server):
```console
$ gpg --send-key $KEYID
```console
and import the newly on any computer where you wish to use it (it will update the key if previously imported):
```console
$ gpg --recv $KEYID
```
This will extend the validity of your GPG key and will allow you to use it for SSH authorization. Note that you do _not_ need to update the SSH public key located on remote servers.
## Rotating keys