Hello,
John Soo wrote:
> Do you have any ideas what might be going on?
In the original message of yours on January 28th, the log has:
==========================
gpg: DBG: finish_lookup: checking key 145FD2ED (one)(req_usage=1,verify)
gpg: DBG: exact search requested and found
gpg: DBG: checking subkey 7374A315
gpg: DBG: subkey might be fine for verification
gpg: DBG: using key 7374A315
gpg: using subkey B67EB1E57374A315 instead of primary key 6E628CC4145FD2ED
gpg: DBG: [no clock] enter pk_verify
gpg: DBG: rsa_verify
data:+01ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[...]
gpg: DBG: rsa_verify
sig:+c64e97c7aa8ea26a172a1589cfc8f60189ae61b895e07d3562e9bf11d60e5f44
\
[...]
gpg: DBG: rsa_verify
n:+c744addf555d5da3828c0c80b5d1d18e94ef5e5933659ed7a669dc1dc2608380 \
[...]
gpg: DBG: rsa_verify e:+010001
gpg: DBG: rsa_verify
cmp:+c742addf555d5da3828c0c80b5d1d18e94ef5e5933659ed7a669dc1dc2608380
\
[...]
gpg: DBG: rsa_verify => Bad signature
==========================
The problem is the line:
n:+c744addf555d5da3828c0c80b5d1d18e94ef5e5933659ed7a669dc1dc2608380
...
According to the other part of the log, it is your RSA public raw
material of your primary key 1510C86404E2F6ECA02871DB6E628CC4145FD2ED.
The problem here is that: the subkey
1B7E30E28F43D2F9469CF62AB67EB1E57374A315 was retrieved correctly, but
the key used for verification was
1510C86404E2F6ECA02871DB6E628CC4145FD2ED for some reason.
If you want to debug further, you don't need to generate multiple
signatures, but do test verification multiple times on a single
signature.
This is my observation. I have no idea why gpg confused
between primary key and subkey on your system occasionally.
--
_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users
