| 1 |
On Sunday 18 Sep 2016 17:00:55 Alecks Gates wrote: |
| 2 |
> On 09/18/2016 04:45 PM, Neil Bothwick wrote: |
| 3 |
> > On Sun, 18 Sep 2016 11:47:05 -0700, Ian Zimmerman wrote: |
| 4 |
> >>> I have seen bad signatures in this M/L but it is not a regular |
| 5 |
> >>> occurrence. |
| 6 |
> >> |
| 7 |
> >> Your own message re: TaskCoach fails to verify, and that's what prompted |
| 8 |
> >> me to post about it here. |
| 9 |
> > |
| 10 |
> > That signature shows as good here using Claws Mail with |
| 11 |
> > app-crypt/gnupg-2.1.5 |
| 12 |
> |
| 13 |
> I can confirm Mick's (and Neil's) signatures are good with |
| 14 |
> mail-client/thunderbird-45.3.0-r1, Enigmail, and app-crypt/gnupg-2.1.15 |
| 15 |
|
| 16 |
|
| 17 |
Hmm ... I am getting confused. My Kmail shows my sig as being Good. |
| 18 |
|
| 19 |
So I save the ascii signature file separately, as well as the whole message. |
| 20 |
Trying to verify the latter with the former on the CLI, gives me a Bad |
| 21 |
signature. :-/ |
| 22 |
|
| 23 |
It's getting late, so I may be doing this wrong? |
| 24 |
========================== |
| 25 |
$ gpg --verify signature.asc message.eml |
| 26 |
gpg: enabled debug flags: memstat |
| 27 |
Version: GnuPG v2 |
| 28 |
gpg: armor header: |
| 29 |
gpg: Signature made Sun Sep 18 17:39:06 2016 BST using RSA key ID F013861E |
| 30 |
gpg: using classic trust model |
| 31 |
gpg: BAD signature from "Michael Kintzios <michaelkintzios@×××××.com>" |
| 32 |
[ultimate] |
| 33 |
gpg: binary signature, digest algorithm SHA256 |
| 34 |
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 |
| 35 |
outmix=0 getlvl1=0/0 getlvl2=0/0 |
| 36 |
secmem usage: 0/65536 bytes in 0 blocks |
| 37 |
========================== |
| 38 |
|
| 39 |
-- |
| 40 |
Regards, |
| 41 |
Mick |
Archives