Although you rarely need to delete subkey, there are situations where you need to like mistakenly created subkeys but not used or the intended usage was scrapped after creation.
However, it is important to note that the sub-key must not be used at all. Otherwise, it is better to publish a revocation certificate instead of deleting the key. (Remember, the public still have the sub-key access).
For advanced users who deleted their "certify" capability secret key, you need to restore it back for key creations. You can verify it by using the following command:
$ gpg --list-secret-keys
Example:
$ gpg --list-secret-keys
...
---------------------------
sec rsa4096 2020-01-10 [C]
AC51A10307C10B2A4BB1C89AF5EF57A0FB4EF0EF
uid [ultimate] "Shotgun" John, Smith (Main ID) <john.smith@email.com>
You want to observe the key with [C
] capability and the sec
label does not have a hash ("sec#
"). If it does, you need to restore the key by loading the backup copy and use the following command to restore it:
$ gpg --import /path/to/you/key.asc
Once done, it's time to create sub-keypairs.
We start off by obtaining your primary key ID and the targeted subkey. This is by using the following command and find your key:
gpg --list-secret-keys
Example:
$ gpg --list-secret-keys
...
---------------------------
sec rsa4096 2020-01-10 [C]
AC51A10307C10B2A4BB1C89AF5EF57A0FB4EF0EF
uid [ultimate] "Shotgun" John, Smith <john.smith@company.com>
uid [ultimate] "Shotgun" John, Smith (Main ID) <john.smith@email.com>
ssb rsa4096 2020-01-10 [S] [expires: 2022-01-09]
ssb rsa4096 2020-01-10 [E] [expires: 2022-01-09]
ssb rsa4096 2020-01-10 [A] [expires: 2022-01-09]
ssb ed25519 2020-01-10 [S] [expires: 2022-01-09]
ssb ed25519 2020-01-10 [A] [expires: 2022-01-09]
ssb cv25519 2020-01-10 [E] [expires: 2022-01-09]
In the example above,
AC51A10307C10B2A4BB1C89AF5EF57A0FB4EF0EF
. Make sure this is the primary key you wanted to export.With the key ID identified, it's time to edit the key. Use the following command pattern to edit the key:
$ gpg --expert --edit-key <key-id>
From the example above, it is:
$ gpg --expert --edit-key AC51A10307C10B2A4BB1C89AF5EF57A0FB4EF0EF
You will be presented with the gpg key editor's main menu. It looks something like:
gpg (GnuPG) 2.2.12; Copyright (C) 2018 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Secret key is available.
sec rsa4096/F5EF57A0FB4EF0EF
created: 2020-01-10 expires: never usage: C
trust: ultimate validity: ultimate
ssb rsa4096/66F2E45747AB2C90
created: 2020-01-10 expires: 2022-01-09 usage: S
ssb rsa4096/9D485C5208D0859F
created: 2020-01-10 expires: 2022-01-09 usage: E
ssb rsa4096/90939A7DBBFC226D
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb ed25519/16972F736B59F874
created: 2020-01-10 expires: 2022-01-09 usage: S
ssb ed25519/D22D6E1FD575E506
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb cv25519/25252612A403B41C
created: 2020-01-10 expires: 2022-01-09 usage: E
[ultimate] (1). "Shotgun" John, Smith <john.smith@company.com>
[ultimate] (2) "Shotgun" John, Smith (Main ID) <john.smith@email.com>
gpg>
Now you can select your sub-key using key
command. Upon selection, you'll notice an asterisk (*
) right after its ssb
label. Keep in mind that the numbering is following N-1
calculation (E.g. option #1 ➔ 0, option #2 ➔ 1). Here's an example for selecting the 5th key (5 - 1 = 4
):
gpg> key 4
sec rsa4096/F5EF57A0FB4EF0EF
created: 2020-01-10 expires: never usage: C
trust: ultimate validity: ultimate
ssb rsa4096/66F2E45747AB2C90
created: 2020-01-10 expires: 2022-01-09 usage: S
ssb rsa4096/9D485C5208D0859F
created: 2020-01-10 expires: 2022-01-09 usage: E
ssb rsa4096/90939A7DBBFC226D
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb* ed25519/16972F736B59F874
created: 2020-01-10 expires: 2022-01-09 usage: S
ssb ed25519/D22D6E1FD575E506
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb cv25519/25252612A403B41C
created: 2020-01-10 expires: 2022-01-09 usage: E
[ultimate] (1). "Shotgun" John, Smith <john.smith@company.com>
[ultimate] (2) "Shotgun" John, Smith (Main ID) <john.smith@email.com>
gpg>
Upon selecting your key, proceed to delete it using delkey
command. GnuPG will ask for (password?) confirmation before proceeding. Once done, you will notice that your selected key is gone.
gpg> delkey
Do you really want to delete this key? (y/N) y
sec rsa4096/F5EF57A0FB4EF0EF
created: 2020-01-10 expires: never usage: C
trust: ultimate validity: ultimate
ssb rsa4096/66F2E45747AB2C90
created: 2020-01-10 expires: 2022-01-09 usage: S
ssb rsa4096/9D485C5208D0859F
created: 2020-01-10 expires: 2022-01-09 usage: E
ssb rsa4096/90939A7DBBFC226D
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb ed25519/D22D6E1FD575E506
created: 2020-01-10 expires: 2022-01-09 usage: A
ssb cv25519/25252612A403B41C
created: 2020-01-10 expires: 2022-01-09 usage: E
[ultimate] (1). "Shotgun" John, Smith <john.smith@company.com>
[ultimate] (2) "Shotgun" John, Smith (Main ID) <john.smith@email.com>
gpg>
Once everything is done, you may quit and save. Type quit and remember to confirm the save.
gpg> quit
Save changes? (y/N) y
Now that everything is completed, you can verify your key again using the following command:
$ gpg --list-secrets-key
This will now yield something as such:
...
---------------------------
sec rsa4096 2020-01-10 [C]
AC51A10307C10B2A4BB1C89AF5EF57A0FB4EF0EF
uid [ultimate] "Shotgun" John, Smith (Main ID) <john.smith@email.com>
ssb rsa4096 2020-01-10 [S] [expires: 2022-01-09]
ssb rsa4096 2020-01-10 [E] [expires: 2022-01-09]
ssb rsa4096 2020-01-10 [A] [expires: 2022-01-09]
ssb ed25519 2020-01-10 [A] [expires: 2022-01-09]
ssb cv25519 2020-01-10 [E] [expires: 2022-01-09]
That's all for deleting GPG Sub-Keypair.