On Sat, 22 Nov 2014 21:12, 2014-667rhzu3dc-lists-gro...@riseup.net said:
> I do not have the key in a newer format, and have not yet investigated
> whether there is any useful way to achieve this. I understand it is
No, you can't convert the key to v4 format.
Salam-Shalom,
Werner
--
Die
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Wednesday 19 November 2014 at 5:07:37 PM, in
, Hugo Hinterberger
wrote:
> I just tried to verify your message, but failed at
> importing your key. GPG tellst me that the key packet
> is of an obsolete version 3. Do you have the key in a
> n
Hi,
this should go to: "MFPA <2014-667rhzu3dc-lists-gro...@riseup.net>", sorry
if it goes on the list "gmane.comp.encryption.gpg.user" too (minor
user/MUA f-), although this might be interesting to Werner Koch also.
I just tried to verify your message, but failed at importing your key.
GPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Monday 17 November 2014 at 11:32:45 AM, in
, Werner Koch wrote:
> Can you produce a test case using sample keys?
So far I have only managed to reproduce it using the keys I already
have. I will try again over the next few days.
- --
Bes
On Sat, 15 Nov 2014 20:45, 2014-667rhzu3dc-lists-gro...@riseup.net said:
> I just got the following error messages from Gnupg 2.1 and Windows
> XP:-
That does not look like a Windows specific problem. However, I can't
replicate it.
>gpg --no-options --no-default-keyring --import "C:\Documen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
I just got the following error messages from Gnupg 2.1 and Windows
XP:-
gpg: O j: ... this is a bug (/home/wk/b-w32/speedo/gnupg-
2.1.0/g10/import.c:1278:transfer_secret_keys)
This application has requested the Runtime to termi
