HOW to upgrade: 2.0.22 --> 2.3.3 ???

[Werner Koch]

On Tue,  8 Oct 2024 13:09, Mike Schleif said:

> Ought we do something on the legacy (v2.0.22) host before copying to the
> new host?

I general not but you can do this:

  gpg --export             >all-public-keys.gpg
  gpg --export-secret-keys >all-secret-keys.gpg
  gpg --export-ownertrust  >ownertrust.txt

also backup the *.conf files if you have some.

On the new machine rename the existsing ~/.gnupg to ~/.gnupg-saved and
then run

  gpg -k

which will create a new ~/.gnupg

Then

  gpg --import <all-secret-keys.gpg
  gpg --import <all-public-keys.gpg
  gpg --import-ownertrust <ownertrust.txt
  gpg --check-trustdb

That avoids any problem with garbage inthe ~/.gnupg.  Check gpg.conf
whether you have any strange keys in them.  Inb particular remove any
references to the old PGP-2 keys.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20241009/a3df372b/attachment.sig>