Re: epg.el: epg--status-GET_LINE not working?

[Teemu Likonen <tlikonen@iki.fi>]

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Daiki Ueno [2017-06-26 09:30:00+02] wrote:

> Teemu Likonen <tlikonen@iki.fi> writes:
>> A possible fix: Remove "--command-fd 0" from gpg's options. It looks to
>> me that it is not really used. Then also epg--status-GET_LINE function
>> can be removed.
>
> It doesn't sound like a good idea. Have you considered all the cases
> where epg--status-GET_LINE is called? It is used (and works) for many
> other queries.

I merely noticed that checking signatures when the message content is
sent through the standard input the "--command-fd 0" doesn't work. Gpg
doesn't wait for "GET_LINE tofu.conflict" input from stardard input; it
just proceeds and gives some "hang up" message. So I concluded that
"--command-fd 0" and GET_LINE just can't work together on epg.el. But
maybe I generalized too much. Maybe the problem is just in this
signature checking operation which goes like this:

    echo message_content | gpg --status-fd 1 --yes --command-fd 0
    --output output_file --verify -- signature_file -

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]