Annoying bug: gpg-agent+gnupg and cancelling in pinentry-* repops pinentry two times

[Marc Mutz]

On Thursday 16 January 2003 23:24, Marc Mutz wrote:
<snip>
> What needs to be done?
> 1. return the information that the user cancelled pinentry from
>    agent_get_passphrase to passphrase_to_dek

I see this is done in 1.2.2rc2

> 2. Extend the status-fd protocol to include a STATUS_CANCELLED
> 3. Make passphrase_to_dek write_status( STATUS_CANCELLED ) in the
> cancel case instead of STATUS_MISSING_PASSPHRASE

This isn't.

> and make it report
> that incident back to it's callers.

This is being done, but the callers all set int*canceled to NULL :-(

> 4. Make the callers of passphrase_to_dek honour the cancel
> information so they don't try two more times.
> 5. Make gpgme recognize the new status and properly return exisiting
> GPGME_Canceled or new GPGME_Externally_Canceled error codes.
<snip>

These are also not there yet.

Is there any chance that this will be fixed in gpg 1.2.2 and gpgme 
0.3.16?

Marc

-- 
It is truly ironic that the United States, once the beacon for
promoting the principles of freedom of expression, is now
systematically infecting other countries with this dangerous public
policy choice [the DMCA] that will restrict more speech than any law
before it.    -- EFF FTAA Alert:
                 Stop Hollywood Forcing Technology Ban on 34 Countries
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 192 bytes
Desc: signature
Url : /pipermail/attachments/20030429/8a3e82b8/attachment.bin