fix: add an explicit example about publishing the pubkey when expiring
parent
fec6e92b8f
commit
619537629f
14
README.md
14
README.md
|
@ -2026,7 +2026,7 @@ Key is valid for? (0)
|
||||||
```
|
```
|
||||||
Follow these prompts to set a new expiration date, then `save` to save your changes.
|
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
|
```console
|
||||||
$ gpg --armor --export $KEYID > gpg-$KEYID-$(date +%F).asc
|
$ 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
|
$ 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.
|
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
|
## Rotating keys
|
||||||
|
|
Loading…
Reference in New Issue