Start Updating gpg key

Updating gpg key

You can update the expiration date, the number of days, or remove the expiration date for your PGP key.

It is possible to select the subkey you will be working on by invoking the key command followed by the number (index) of the subkey you wish to select.

(Note that with the check disabled, you see a warning when you install new packages, but the installation still succeeds.) If you have explicitly configured the GPG check, you need to replace the key.

You can check the authenticity of locally downloaded packages by running the The Free BSD package management system does not use a GPG key, so no action is necessary.

Even if you lose the private key or forget the passphrase or even lose the revocation certificate too, a time will come that the public key will expire, which indicates that it is invalid and should not be trusted any more. In this section I describe how to extend or reset a key’s expiration date using gpg from the command line.

There are probably several graphical front-ends out there that might simplify this procedure, but, since graphical frontends are not usually cross-platform, I choose to use the command-line gpg utility. First of all, you have to know the ID of the key you need to edit: list pub 1024D/B989893B created: 2007-03-07 expired: 2009-12-31 usage: SCA trust: ultimate validity: ultimate sub 4096g/320D81EE created: 2007-03-07 expired: 2009-12-31 usage: E [ ultimate] (1).

On the other hand, you can always extend the key’s expiration date and send the updated key to the key servers.

When others find out that your public key has expired, the very first thing they do will be to refresh it from a key server, in which case they’ll retrieve your updated public key.

By default, the check is disabled for NGINX and NGINX Plus repositories, but enabled for NGINX Amplify repositories.