Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-12 Thread Philip Jackson 
On 11/12/15 22:42, MFPA wrote:
> 
>> > On my laptop, with Debian Jessie and gpg2.1.7, the
>> > signature verifies ok.  Again normal for 2.1.x
> Do both signatures verify correctly for you with 2.1.x, or does
> Enigmail still only pass on the result of one of them?
> 

I don't use the laptop regularly for mail but I did update its inbox
today just to check out what it does now.

gpg2.1.7 with enigmail 1.9a1 of 30 Nov 2015 verifies all your emails of
2015 as 'good signature'.  However, when I look to see more details, the
verification behind the enigmail 'Details' button quotes key ID
0x547B7194 which is the RSA 2048 public key identity.

But when I look into the enigmail log, there I see that signatures were
made by both EDDSA subkey 0x1712BC461AF778E4 and RSA subkey
0x6B7C74CEB31F25F0.

Getting back to the desktop --

On my desktop with 2.0.22 with enigmail 1.9a1 of 8 Oct 2015, enigmail
provides differing info depending on whether you're inline or pgp/mime.

The latter gives the more alarming info behind enigmail's Details button
"Untrusted bad signature "

But again, enigmail's logfile shows both subkeys were used.  Enigmail
doesn't use the available info which is there in the logfile wrt the RSA
key ...(I quote from the logfile)...

"using subkey 0x6B7C74CEB31F25F0 instead of primary key 0x251BCCEB547B7194
gpg: using PGP trust model
gpg: key 0x26BD500A23543A63: accepted as trusted key
gpg: Good signature from "MFPA" [unknown]
gpg: aka "2014-667rhzu3dc-lists-gro...@riseup.net
<2014-667rhzu3dc-lists-gro...@riseup.net>" [unknown]
gpg: aka "0x251BCCEB547B7194" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!"

Never mind the trust issue.  The logfile does show "good signature".


Philip




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-11 Thread Brian Minton 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I got the following message:
rejected by import screener

Here's more detail (gpg 2.1.8 on Windows 8):

C:\Users\mintonb>gpg -vvv --recv 0x1712BC461AF778E4
gpg: using character set 'CP437'
gpg: data source: http://pgp.mit.edu:80
gpg: armor: BEGIN PGP PUBLIC KEY BLOCK
gpg: armor header: Version: SKS 1.1.5
gpg: armor header: Comment: Hostname: pgp.mit.edu
# off=0 ctb=99 tag=6 hlen=3 plen=269
:public key packet:
version 4, algo 1, created 1415500876, expires 0
pkey[0]: [2048 bits]
pkey[1]: [17 bits]
keyid: 251BCCEB547B7194
# off=272 ctb=b4 tag=13 hlen=2 plen=4
:user ID packet: "MFPA"
# off=278 ctb=89 tag=2 hlen=3 plen=322
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1415582356, md5len 0, sigclass 0x13
digest algo 10, begin of digest 24 eb
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2014-11-10)
hashed subpkt 25 len 1 (primary user ID)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2048 bits]
# off=603 ctb=89 tag=2 hlen=3 plen=322
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441185092, md5len 0, sigclass 0x13
digest algo 10, begin of digest f2 40
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2015-09-02)
hashed subpkt 25 len 1 (primary user ID)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2042 bits]
# off=928 ctb=b4 tag=13 hlen=2 plen=18
:user ID packet: "0x251BCCEB547B7194"
# off=948 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1416188694, md5len 0, sigclass 0x13
digest algo 10, begin of digest a3 61
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created 2014-11-17)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2048 bits]
# off=1270 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441185086, md5len 0, sigclass 0x13
digest algo 10, begin of digest 58 9d
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 2 len 4 (sig created 2015-09-02)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2045 bits]
# off=1592 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1416145056, md5len 0, sigclass 0x13
digest algo 10, begin of digest 30 1c
hashed subpkt 2 len 4 (sig created 2014-11-16)
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
subpkt 16 len 8 (issuer key ID 251BCCEB547B7194)
data: [2044 bits]
# off=1914 ctb=b4 tag=13 hlen=2 plen=81
:user ID packet: "2014-667rhzu3dc-lists-gro...@riseup.net <2014-667rhzu3dc-lists
- -gro...@riseup.net>"
# off=1997 ctb=89 tag=2 hlen=3 plen=319
:signature packet: algo 1, keyid 251BCCEB547B7194
version 4, created 1441159293, md5len 0, sigclass 0x13
digest algo 10, begin of digest 96 2d
hashed subpkt 27 len 1 (key flags: 01)
hashed subpkt 11 len 10 (pref-sym-algos: 13 9 8 12 7 3 11 10 4 2)
hashed subpkt 21 len 6 (pref-hash-algos: 10 9 8 11 3 2)
hashed subpkt 22 len 4 (pref-zip-algos: 3 2 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
hashed subpkt 2 len 4 (sig created

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-11 Thread Brad Rogers 
On Fri, 11 Dec 2015 21:35:56 +
MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> wrote:

Hello MFPA,

>1.4.x should verify the signature from my RSA subkey but report "Can't
>check signature: unknown pubkey algorithm" for the signature from my
>EDDSA subkey.

Unfortunately, GPGME and Claws Mail (probably) interfere with the error
reporting.  No matter.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Loaded like a freight train flyin' like an aeroplane
Nightrain - Guns 'N' Roses


pgp2ObXJklwD2.pgp
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-11 Thread MFPA 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi


On Thursday 10 December 2015 at 1:05:15 PM, in
, Philip Jackson wrote:



> I'm using gpg2.0.22 on my desktop and I can never
> verify your emails (MFPA) - I always get from enigmail
> :

> "Unverified signature; the key type is not supported by
> your version of GnuPG"

> "Unverified signature

> UNTRUSTED BAD signature from
> 2014-667rhzu3dc-lists-gro...@riseup.net
> <2014-667rhzu3dc-lists-gro...@riseup.net>"

> Which is normal for an ECC key.


Except that "Unverified" is not the same as "BAD".

And Enigmail is failing to pass on GnuPG's output from verifing the
signature made with my RSA key.



> On my laptop, with Debian Jessie and gpg2.1.7, the
> signature verifies ok.  Again normal for 2.1.x

Do both signatures verify correctly for you with 2.1.x, or does
Enigmail still only pass on the result of one of them?


- --
Best regards

MFPA  

Time flies like an arrow. Fruit flies like a banana. -- Groucho Marx
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWa0MtXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwc+8IALf022WwZZ7EQWHopVGRaGjS
7z+nIQHzqjcdKa8GeCSkQlNO9BKG4sMZsi3gngsgbELKaqHNeIYbve3Y783vfFKT
3Yv7qayAS4B0ygkI90okOAH56ai7XUtu0blvphvx/IBE6w2VVqkFZXIrO8htJ3iS
KuJpYD9JyIz40bY8rgz3Hs2/B89XtOU8F/YEJd/374z4ptET7Wk7/xtijsGna0Bl
A+J8EVyY9GHGtX0qAb0MNR9IyvpkM9YX+fPx4XTKbIqM9KEbvaTq1UZCjZ8a+oOA
Pqo9pzUc502i6mscyHKFtDeOvlcnHSzTvAdFeN4vnWIZ8nJJxXzkZf/pJ3R2FX+I
vgQBFgoAZgUCVmtDLV8UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45Gw2AP0erl6yVwMdgznCBB+5Gh/gTyWq
8m1Cfce28LPcqqB8iAEAr9g2cKnk3oua/DWRksEndTUogjRF4/y3ieK/XFtoDQI=
=LPUB
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-11 Thread MFPA 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi


On Thursday 10 December 2015 at 9:46:31 AM, in
, Brad Rogers
wrote:




> GnuPG v1.4.19

1.4.x should verify the signature from my RSA subkey but report "Can't
check signature: unknown pubkey algorithm" for the signature from my
EDDSA subkey.


> There's also one
> other difference; The signature is no longer inline,
> but attached.  Not that I expect that is relevant.


Yes, I accidentally used PGP/MIME instead of inline.



- --
Best regards

MFPA  

Vegetarian: Indian word for lousy hunter!!!
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJWa0INXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwtWsH/0pus4Fby0eWHiXwRMKeUStc
UiTWl/rE/w6wmnDA6gTqUuDZQSQoiJxS37xJjAHJmE0OESC/1IjUA1pTLsq+Hdwh
UkXUerOPjazzJhoLhMxAhCXshzxov89wARbeOSqr+J2IHukrgOt6tJ7jfCbmx6mm
S/9LJNyCQ81GoGAaMq2HvFnyOatAH7K0pIi9swehZ8XyorBQc7CeziO6NVgxsNAz
ieFKCXJYGdS32z6QAg7Et/pIzKU2xNstciVLNa5AXYZ2/5Z5wOvsPsahRCaSm+w9
bomPBfbyiFGp3dtPe8OBDGORdFjfqIHEwfkgTw3i+QImiGs8R3Ke/qZw4ojFC2iI
vgQBFgoAZgUCVmtCE18UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45CUpAPwNDCXop+tmAs1zatvZDU9unmrE
7s9UEsiv+dhjvjZmwgD/WBOn4QBjSjp+lsChmRszLD/0UKS8QL/cC3L7lj+eWQU=
=xLr5
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-10 Thread Philip Jackson 
On 10/12/15 01:50, MFPA wrote:
> On 6th December I switched the order of these lines, so that the RSA
> signature comes last. An Enigmail and GnuPG 2.0 user told me he was
> not seeing the "good" signature from 0x6B7C74CEB31F25F0. It appears
> that if there are multiple signatures present, Enigmail only passes on
> the GnuPG output for the last one.

I'm using gpg2.0.22 on my desktop and I can never verify your emails
(MFPA) - I always get from enigmail :

"Unverified signature; the key type is not supported by your version of
GnuPG"

"Unverified signature

UNTRUSTED BAD signature from 2014-667rhzu3dc-lists-gro...@riseup.net
<2014-667rhzu3dc-lists-gro...@riseup.net>"

Which is normal for an ECC key.

On my laptop, with Debian Jessie and gpg2.1.7, the signature verifies
ok.  Again normal for 2.1.x

Philip



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-10 Thread Brad Rogers 
On Thu, 10 Dec 2015 00:50:23 +
MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> wrote:

Hello MFPA,

>Which GnuPG version are you using?

Damn;  I always forget some vital bit of info

GnuPG v1.4.19

>Maybe if there are multiple signatures present, your MUA only 
>passes on the GnuPG output for the first one? I just switched them back 

No idea, TBH - I don't understand coding well enough to figure it out.
I'll ask on the CM list and see what they say.

>round to see what happens.

This message validated correctly.  There's also one other difference;
The signature is no longer inline, but attached.  Not that I expect that
is relevant.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
You never listen to a word that I said
Public Image - Public Image Ltd


pgp48fkR_W7X8.pgp
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-09 Thread MFPA 
Hi


On Tuesday 8 December 2015 at 11:24:36 PM, in
, Brad Rogers
wrote:


> It's the same for me;  A re-import of your key still
> results in an error(1).  

Which GnuPG version are you using?




> I've checked some (locally)
> archived emails from you (received via this list) and
> they verify fine.  Obviously, something's changed, but
> IDK what.  Whatever the change, it occurred between 15
> Nov and 7 Dec.  I have a message from the earlier date
> that verifies and a message from the latter date that
> doesn't.  Consequently, I believe the issue is
> something other than your keyfile.


I have two "local-user" lines in my gpg.conf file, 0x1712BC461AF778E4!
and 0x6B7C74CEB31F25F0!. The aim is a signature from EDDSA subkey
0x1712BC461AF778E4, but also a signature from my RSA subkey
0x6B7C74CEB31F25F0 that can be verified by GnuPG 1.4 or 2.0 versions.

On 6th December I switched the order of these lines, so that the RSA
signature comes last. An Enigmail and GnuPG 2.0 user told me he was
not seeing the "good" signature from 0x6B7C74CEB31F25F0. It appears
that if there are multiple signatures present, Enigmail only passes on
the GnuPG output for the last one.



> If it helps, I use a self-compiled (from GIT) Claws
> Mail as my MUA.

Maybe if there are multiple signatures present, your MUA only 
passes on the GnuPG output for the first one? I just switched them back 
round to see what happens.


> (1) Different error message "The signature can't be
> checked - End of file."  






-- 
Best regards

MFPA  

To steal ideas from one person is plagiarism; 
to steal from many is research.

pgplBuw39yCVE.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-08 Thread Brad Rogers 
On Tue, 8 Dec 2015 22:47:19 +
MFPA <2014-667rhzu3dc-lists-gro...@riseup.net> wrote:

Hello MFPA,

>I suggested he delete my key and re-import it. He tells me he tried
>that twice and it didn't help. It's a mystery to me.

It's the same for me;  A re-import of your key still results in an
error(1).  I've checked some (locally) archived emails from you
(received via this list) and they verify fine.  Obviously, something's
changed, but IDK what.  Whatever the change, it occurred between 15 Nov
and 7 Dec.  I have a message from the earlier date that verifies and a
message from the latter date that doesn't.  Consequently, I believe the
issue is something other than your keyfile.

If it helps, I use a self-compiled (from GIT) Claws Mail as my MUA.

(1) Different error message "The signature can't be checked - End of
file."

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Gary don't need his eyes to see.  Gary and his eyes have parted company
Gary Gilmore's Eyes - The Adverts


pgpXTCfE6Q3vf.pgp
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-08 Thread MFPA 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi


On Tuesday 8 December 2015 at 8:26:23 AM, in
, NIIBE Yutaka wrote:



> I don't think that GnuPG frontend or gpg-agent doesn't
> emit this error.

> It could be libgcrypt which generates this error.

It seems to be defined in Libgpg-error, which "defines common error
values for all GnuPG components."



> I validate your e-mail by the key of 0x1712BC461AF778E4
> with no error.

So do I.



> So, I don't think there is a problem in
> your key.  The local copy of your public key in his
> computer would be a problem.

I suggested he delete my key and re-import it. He tells me he tried
that twice and it didn't help. It's a mystery to me.


- --
Best regards

MFPA  

The man who really wants to do something finds a way,
the other finds an excuse.
-BEGIN PGP SIGNATURE-

iL4EARYKAGYFAlZnXgVfFIAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
bnBncC5maWZ0aGhvcnNlbWFuLm5ldDMzQUNFRDRFRTkxMzRFRUJERTZBODUwNjE3
MTJCQzQ2MUFGNzc4RTQACgkQFxK8Rhr3eOSMUwD/TAoSg7DIEsekEyNnuKee3eh+
TUJDOCmpRU29m4i8TFMA/AsPpuDegLO+snCiqxKeIyLUvVMMhWmcnwYM5v9M9IID
iQF8BAEBCgBmBQJWZ14KXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwEagIALJa/sbbSF6MSDNm/EhecLw7
gOBCOX9NCx+phXX4lGFbWGCm97QFp8be3kNFa64cpXKWFc7IoVCXWyS8wlhsH99q
5af9ZLOaV2RfaJEIe8JGErqC8nD8cfCwlUN42JSwzy3OW+3eBVQO0o30UzUygKPp
lYUmz8SUGeFoxnRzRy45gF/eA1ytI1jcT3mqGVyE4+q7TzQk5BrSzyvuKBZL5UNI
Jp1ECj3lyK06PXLJe2vfwoAQcbLNnHe5GD2bjzb9i3pTLsuksMpiUegzVjT1UcFX
rzqNsvqceCHIxlshaACFVXvOTxAaCGGd73MEq7zIMU8QBU1SSLgYgmh7ZZKiiCs=
=3cNb
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Error message "gpg: Can't check signature: Broken public key"

2015-12-08 Thread NIIBE Yutaka 
On 12/08/2015 08:51 AM, MFPA wrote:
> What does the error message "gpg: Can't check signature: Broken public
> key" mean?
> 
> One of the members of PGPNET reports getting that error
> message when verifying the signatures on my signed and encrypted
> messages to the group. He gets it for the signatures from my EDDSA subkey
> 0x1712BC461AF778E4, and says he uses GnuGP 2.1.8.

I don't think that GnuPG frontend or gpg-agent doesn't emit this
error.

It could be libgcrypt which generates this error.  EdDSA key is
represented by a point on the Ed25519 curve.  When the point is not on
the curve (the key is invalid), it complains by this error.

I validate your e-mail by the key of 0x1712BC461AF778E4 with no error.
So, I don't think there is a problem in your key.  The local copy
of your public key in his computer would be a problem.
-- 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Error message "gpg: Can't check signature: Broken public key"

2015-12-07 Thread MFPA 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



What does the error message "gpg: Can't check signature: Broken public
key" mean?

One of the members of PGPNET reports getting that error
message when verifying the signatures on my signed and encrypted
messages to the group. He gets it for the signatures from my EDDSA subkey
0x1712BC461AF778E4, and says he uses GnuGP 2.1.8.


The only references I can find (eg [0]) say:-

  592 GPG_ERR_BROKEN_PUBKEY Broken public key
  593
  594 The public key was mathematically not correctly generated.



[0]
<http://fossies.org/windows/misc/gnupg-w32-2.1.10_20151204.tar.gz/gnupg-w32-2.1.10/PLAY/src/libgpg-error/doc/errorref.txt>


- --
Best regards

MFPA  <mailto:2014-667rhzu3dc-lists-gro...@riseup.net>

Why is the universe here? Well, where else would it be?
-BEGIN PGP SIGNATURE-

iL4EARYKAGYFAlZmG4xfFIAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
bnBncC5maWZ0aGhvcnNlbWFuLm5ldDMzQUNFRDRFRTkxMzRFRUJERTZBODUwNjE3
MTJCQzQ2MUFGNzc4RTQACgkQFxK8Rhr3eORUAAD/XZQqwtz7Q1+Lem/ev5EwrE9O
BJCWG/6+dlyAvQSogR0BANsB14r4s6s+Udhd35Zhj/m4q3cOZ84thFqB5hNT3lkK
iQF8BAEBCgBmBQJWZhuZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwpS0H/ipta+E5Dq7f3+aDnpDbAJJS
4XFUM6tmJY2AdAzRqhxjSsCRmCkyekZX9R9CPGT2RlqYRJfqFLSSODka8VIMA4kk
XYuJo+AK9+LnDSVh0/G4DKjPRb67CZCT9Fx4UH+6uFrtQTsTWcACb2xzQE62fkxr
ntMNwROqo90D4mbEemUTvv33rSl/00KysbJC3eg9ybbIjNpn1hO/VtIAK9ipF3iU
3NPwXHgmJk5sJ6esyS1Eqtm0QkckZa/sHAV1GrRtKC91k9d4/4qzdK96MKkKLbdo
rUClB8SF3YsO1KwxxbOT0RiUUAa5MUMvwm1oPmEKtw9XymImQDZ7IaR3VoE8ko4=
=td+o
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users