[Enigmail] Problem with automated decryption of encrypted drafts? (Key unlocking popup nightmares)

[Daniel Kahn Gillmor]

On 01/02/2013 04:55 AM, Patrick Brunschwig wrote:
> On 01.01.13 19:57, Sini Ruohomaa wrote:
>> 1) The request popup to unlock my key blocks my _entire X session_,
>> also when TB is minimized, which I think seems needlessly rude. It
>> also doesn't cache my 'cancels' (so I can be asked for the password
>> for 5+ times in a row before I can go back to doing whatever I was
>> doing) and doesn't indicate what it needs the key for. (To
>> reproduce, cause the key popup to appear and just try to ignore
>> it.)
> 
> That's because pinentry blocks your X session. pinentry is part of
> GnuPG 2.x, and there is nothing Enigmail could do about it. AFAIR
> there is an option in gpg-agent.conf to disable blocking the X session.

Bug reports or suggestions about pinentry behavior should probably go to
a gnupg list (i've cc'ed gnupg-users here, please follow up appropriately)

Do any gnupg contributors have suggestions about the "fails to cache my
'cancels'" concern Sini raised above?  I'm not sure how the pieces could
fit together to improve the user experience without breaking
expected/desired behavior in other contexts.

	--dkg


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1027 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20130102/0e709d50/attachment.pgp>