On Mon 2018-11-12 18:27:59 +0100, gnupgpacker wrote:
>> the "classic" version of GnuPG (the 1.4.x series) not only does not
>> ...
>> If you upgrade to the modern version of GnuPG on your windows machine,
>> and then try to re-import, i think you'll find the merge issue resolved.
>
> GnuPG 1.4.23
Hello,
and thanks for reply!
> the "classic" version of GnuPG (the 1.4.x series) not only does not
> ...
> If you upgrade to the modern version of GnuPG on your windows machine,
> and then try to re-import, i think you'll find the merge issue resolved.
GnuPG 1.4.23 is part of GnuPG-Pack with old
Hi there--
On Mon 2018-11-12 11:04:09 +0100, gnupgpac...@on.yourweb.de wrote:
> there occurs an issue while exporting/ importing keypair from
> Windows-7/GPG-1.423 to Android-8.1/R2mail2.
1.423 is not a valid GnuPG version, so i assume you meant GnuPG 1.4.23.
the "classic" version of GnuPG (the
fwiw, i agree with Damien that the existing text in the FAQ about
generating a revocation certificate should be removed.
I think that there should be some text like "where can i find my key's
revocation certificate?" which could be added to the FAQ.
However, situations like these:
On Sat 2018-11
Hello,
there occurs an issue while exporting/ importing keypair from
Windows-7/GPG-1.423 to Android-8.1/R2mail2.
Private/public key contains one main key and three subkeys, all valid til
31.12.2019:
pub xDDDC C
sub x5B9E A
sub x493D S
sub x2BE6 E
But if exporting and importing whole key, subkey
