Mailing List Archive

Finally moving from 2.0.22 to 2.2.x or higher
What do we need to know about using our existing keyring, and copious CLIs,
that we use to encrypt, decrypt and administer our legacy GPG?

As previously posted, we are on Centos 7.9.2009, which only supports GPG
v2.0.x.

Until we upgrade Centos later this year, I've been reviewing suggestions on
how to upgrade to 2.2.17 and higher, which we're about to undertake.

How can we "import" our existing keyring into newer GPG?

What else do we need to know, and prepare for, for our production use?

Please, advise. Thank you.

~ Mike
Re: Finally moving from 2.0.22 to 2.2.x or higher [ In reply to ]
On Sat, 20 May 2023 11:20, Mike Schleif said:

> How can we "import" our existing keyring into newer GPG?

You actually don't need to do anything. gpg auto-migrates the private
keys. If everything works then for you, you may delete the secring.gpg
which is not anymore used (but better take a backup). Your private keys
will then be in private-keys-v1.d/ and a file
~/gnupg/.gnupg-v21-migrated shows thathe migration was successful.



Shalom-Salam,

Werner

--
The pioneers of a warless world are the youth that
refuse military service. - A. Einstein