[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: epg.el: epg--status-GET_LINE not working?
|
From: |
Neal H. Walfield |
|
Subject: |
Re: epg.el: epg--status-GET_LINE not working? |
|
Date: |
Thu, 06 Jul 2017 21:42:14 +0200 |
|
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
At Wed, 05 Jul 2017 22:03:30 +0300,
Teemu Likonen wrote:
> Daiki Ueno [2017-07-05 18:25:29+02] wrote:
> > Teemu Likonen <address@hidden> writes:
> > Anyway, I would rather ignore "tofu.conflict" like the attached patch
> > (not tested), until it becomes really useful.
>
> I agree but with a small addition. That skips the "GET_LINE
> tofu.conflict" case (which I think is good) but user is left without any
> information about what happened. Function epg-signature-to-string will
> return a string like this:
>
> Good signature from [keyid] [user id] created at
> 2017-07-05T21:25:57+0300 using RSA
>
> The signature is good but the usual "(trust ...)" is missing so there is
> no information about key's validity. I suggest adding just the tofu
> conflict info. With a patch like below the mentioned function would
> return:
>
> Good signature from [keyid] [user id] (trust: tofu-conflict) created
> at 2017-07-05T21:25:57+0300 using RSA
Why not implement TOFU support properly by showing the conflict and
allowing the user to resolve it instead of what appears to me to be a
workaround?