bastian/debyl-site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gpg_update_key Fixed typos

Browse Source
This commit is contained in:
Bastian de Byl
2020-02-17 17:20:38 -05:00
parent 122414a2bf
commit 71e9032215
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
content/post/updating_gpg_key.md
View File

@@ -7,7 +7,7 @@ categories: ["Blog"]
contentCopyright: false contentCopyright: false
hideHeaderAndFooter: false hideHeaderAndFooter: false
--- ---
It's a good idea to update your GPG key(s) before they expires. Mine is set to It's a good idea to update your GPG key(s) before they expire. Mine is set to
expire year, from whence I last updated the expiration. Let's explore how this expire year, from whence I last updated the expiration. Let's explore how this
is done! is done!
@@ -89,7 +89,7 @@ sec rsa4096 2017-11-21 [SC] [expires: 2021-02-16]
``` ```
### Update ### Update
Updating the primary secret key and all it's subkeys is done via `gpg` in the Updating the primary secret key and all it's sub keys is done via `gpg` in the
following manner: following manner:
``` ```
gpg --edit-key your@email.address gpg --edit-key your@email.address
@@ -113,7 +113,7 @@ Is this correct? (y/N) y
gpg> save gpg> save
``` ```
At this point, it's a good idea to send the key to the keyserver: At this point, it's a good idea to send the key to the key server:
```bash ```bash
gpg --send-keys your@email.address gpg --send-keys your@email.address
# or # or
@@ -139,7 +139,7 @@ gpg --import /mnt/media/some/dir/secretsubkey.gpg
### Verification ### Verification
Once **only** the secret sub-key has been imported from the previous step, it Once **only** the secret sub-key has been imported from the previous step, it
should be verified that the primary secret key is **not** in your keychain should be verified that the primary secret key is **not** in your keyring
(partial stripped key designated via `sec#` in the following): (partial stripped key designated via `sec#` in the following):
``` ```
gpg --list-secret-keys gpg --list-secret-keys
@@ -159,11 +159,11 @@ attempt this again should you have to, but do so carefully.
Lastly, remember to remove any local back-ups of the keyring or keys you stored Lastly, remember to remove any local back-ups of the keyring or keys you stored
on the host! These should _only_ exist on the encrypted external device. on the host! These should _only_ exist on the encrypted external device.
To unmount the LUKS[^1] encrypted device, it's just one additional step to the To un-mount the LUKS[^1] encrypted device, it's just one additional step to the
usual `umount`: usual `umount`:
```bash ```bash
umount /mnt/media umount /mnt/media
cryptestup --type luks close encryptedusb cryptsetup --type luks close encryptedusb
``` ```
That being done, it is safe to remove the external device! That being done, it is safe to remove the external device!