> If using the clipboard is unsafe, then GPG would disallow its use in
> password managers as well, would it not?
How would it do so?
> If one is supposed to have long, complicated,
> difficult-to-remember-and-type passwords (which one cannot even see
> when they are being entered!), then one
On 20200426, Scott C Jacobs via Gnupg-users wrote:
The problem is, that even if I have a terminal window open into which I wanted
to type xwininfo and xprop,
once the passphrase window appears, I cannot use the terminal or anything else
- the passphrase window allows
nothing to happen until I
Hi,
Not sure how to send this to the right person, so please forward if you
will.
I noticed that `GnuPG Shell` appears to be old.
Debian doesn't have it in it's repository, or at least I can't find it.
Best package I can find is v 1.0.0
On 4/26/20 1:53 PM, Scott C Jacobs via Gnupg-users wrote:
The problem is, that even if I have a terminal window open into which I wanted
to type xwininfo and xprop,
once the passphrase window appears, I cannot use the terminal or anything else
- the passphrase window allows
nothing to happen
>To find out what process is controlling a window, you could use xwininfo and
>xprop as described in this SO answer:
>https://unix.stackexchange.com/a/84981
The problem is, that even if I have a terminal window open into which I wanted
to type xwininfo and xprop,
once the passphrase window
> On 26 Apr 2020, at 05:04, Scott C Jacobs via Gnupg-users
> wrote:
>
> I don't know which of the many GPG packages throws up the passphrase window,
> to know to which package a bug
> report should be directed (if it is a bug). I might have thought
> pinentry[*], but it is NOT one of the
