Here on a Debian system I use mainly
gpg2. Some (Debian packaging/signing) tools use
gpg1 internally, and changing them as it should be would be infeasible.
Both my gpg versions are using the same work directory (
~/.gnupg) and their databases / configuration seem mainly compatible. An exception for this is the handling of the private keys.
As I experienced, private keys created by
gpg2 are not visible for
gpg1 (but their public pairs are).
Digging a lot on the net, as I understand, the
gpg versions are using different files (and maybe different formats) below
~/.gnupg to store them. There are also various one-line solutions to convert the
gpg2 database to
gpg1 and vice versa.
Now I have to use mainly
gpg2, but I have to allow also
gpg1 to work. My idea for this task is that
- I export the gpg2 private key database.
- I import it with
The expected result would be that I can see the same public and private keys with both gpg versions.
Is it possible? Could it work? How can I do that?
(Note: at least Ubuntu and Mint uses already
gpg2 for packaging tasks, but Debian still doesn't.)