Pinentry grabbing keyboard and mouse

[Andre Heinecke]

Hi,

On Thursday 13 April 2017 16:26:12 William L. Thomson Jr. wrote:
> In looking at the QT and the newly added FLTK versions. I noticed
> neither seem to be, unless I missed something, grabbing the keyboard
> and mouse as the GTK version does.
> 
> I am not sure if that is legacy or the proper way. Or why other versions
> do not seem to have that feature. Not sure if it is a requirement that
> pinentry be blocking, take over keyboard and mouse. Such that the
> window cannot be moved, nothing else done till passphrase entered,
> confirmation, etc. Or that was just the choice of the GTK author at the
> time of making that version.
> 
> Which is the correct way?
> Is there a requirement on grabbing keyboard and mouse?
> How come other versions seem to lack such feature?

Speaking for Qt I "recently" changed that behavior from a global grab to a 
focus depending grab. Now only when the input field has focus the keyboard is 
grabbed, with the intention to protect a bit against dumb keyloggers.

The discussion about this can be found here:

https://lists.gnupg.org/pipermail/gnupg-devel/2016-June/031277.html

The biggest concern speaking for the global grab was, as I understood it, that 
it might help users not to enter their passphrase in the wrong window (e.g. a 
chat window).

My personal opinion is that the usability cost of global grabbing from a popup 
Window is too great for that advantage though. But others have different 
Opinions.

> I just want to be consistent with other versions. Also meet project
> requirements, etc.

I don't think there is any grabbing requirement.

Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20170418/0b83e145/attachment.sig>