1
0
mirror of synced 2025-12-22 03:16:52 -05:00
Files
docs/content/github/authenticating-to-github/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md
2021-06-24 11:02:53 -07:00

1.4 KiB

title, intro, redirect_from, versions, topics, shortTitle
title intro redirect_from versions topics shortTitle
Updating an expired GPG key When verifying a signature, {% data variables.product.product_name %} checks that the key is not revoked or expired. If your signing key is revoked or expired, {% data variables.product.product_name %} cannot verify your signatures. If your key is revoked, use the primary key or another key that is not revoked to sign your commits.
/articles/updating-an-expired-gpg-key
/github/authenticating-to-github/updating-an-expired-gpg-key
fpt ghes ghae
* * *
Identity
Access management
Update expired GPG key

If your key is expired, you must update the expiration, export the new key, delete the expired key in your GitHub account, and upload the new key to GitHub. Your previous commits and tags will show as verified, as long as the key meets all other verification requirements.

If your key is invalid and you don't use another valid key in your key set, but instead generate a new GPG key with a new set of credentials, then your commits made with the revoked or expired key will continue to show as unverified. Also, your new credentials will not be able to resign or verify your old commits and tags.

Further reading