Sorry for the delay, the passphrase is 512 characters long (now I should change
it after publishing that here ;-)) and just ascii characters.

With GnuPG 1.x, Enigmail takes care of presenting the passphrase dialog.
With GnuPG 2.x GnuPG does it of its own. For that it spawns a small tool
called pinentry which asks for the passphrase. We actually have several
versions of that pinentry. The one you are using is based on Qt (a toolkit) and
has a limit of 256 bytes for the passphrase. The limit may actually be lower if
you are using non-ascii characters, but I can't see how that value is not
sufficient.

How long is your passphrase and does it contain many non-ascii characters (e.g.
Umlauts)?

Hello, Thank you for your reply.

I used the gpg4win-2.2.1.exe binary which I downloaded from gpg4win.org

The popup I mentioned is the screen that asks me for my password when I try to
open an encrypted mail in my mailbox via thunderbird/enigmail. See the
screenshot. In the newer gpg version this popup is replaced by a prompt screen
that says pinentry and will allow only for shorter passwords.

I understand that my password is exceptional long, as I still was (and maybe
still am) a beginner on the encrypted mail part. But backwards compatibility
seems pretty important in the case of encrypted mails and passwords to decrypt them.

What do you mean by "openpgp popup"?

Which installation options did you used whethn installing gpg4win? Depending on
the version you get a different pinentry version - we have a qt based one, a GTK
based base, and a very simple native windows pinentry.

For the record. This is now optional in pinentry 0.8.4 you can pass
--enable-pinentry-qt4-clipboard to configure to enable clipboard and paste support.

pkg-config variant.

There is also ncurses-config option...

D172: 374_pinentry-0.8.2-ncurses-pkg-config.patch

try starting pinentry with these options (ASSUAN commands) where $TTY and $LANG
are correctly set in current environment

OPTION ttyname=$TTY
OPTION lc-ctype=$LANG

D160: 360_pinentry-gtk2.patch

Please re-open if you still see this problem.

Meanwhile even 2.0.18 is out. Closing it.

See also T1370

Duplicate of T1370

This is on purpose for the GTK version. The authors of the Qt version obviously
think that this is not important.

strange thing is that this works with pinentry-qt

Screenshot shows the small textfield.

(The height of the passphrase textfield is too small)

tested with gnupg 2.0.18 and pinentry 0.8.0 pinentry-qt4 starts in background
tested with gnupg 2.0.18 and pinentry 0.8.1: pinentry-qt4 starts in foreground
as excepted.

These are the versions in Debian squeeze.
The same happens with gnupg 2.0.17 and pinentry 0.8.0, we have not tested 0.8.1 yet.

gnupg 2.0.14 ? You should uodate this before reporting a bug.
pinentry 0.8.1 was released 10 months ago - please test with that one first.

Confirmed with different user accounts and window managers (KDE, stumpwm, ...).
The qt3 version works without problems.

Please direct such questions to a mailing list. This is a bug tracker and not a
support forum.

Please direct such questions to a mailing list. This is a bug trcker and not a
support forum.

Please direct such questions to a mailing list. This is a bug trcker and not a
support forum.

Testing pinentry-qt Version: 0.8.0.svn234-0kk1 (the changelog indicates
that the change is in) on Debian Lenny with KWin from KDE 3.

May we close this bug now?

I did not have a chance to test 2.0.17 or the patch yet, but for the archive:
I just have an instance of gpg-agent, which does not allow ttys matching
"/dev/pts/??", i.e. two digits. On three-digit-ttys it works. Maybe the
behaviour depends on the length of tty when the gpg-agent was started first or
something similar.

A 2.0.17 will be released soon.

oops. Website fixed. The branch names are
STABLE-BRANCH-2-0
STABLE-BRANCH-1-4
Note the dashs. We don't use a dot because the names date back to CVS and that
does not allow a dot in the name.

From http://gnupg.org/download/cvs_access.en.html:
the stable 2.0 version (currently version 2.0.16) is known as STABLE-BRANCH-2.0;
the stable 1.4 version of GnuPG (1.4.11) is known under as STABLE-BRANCH-2.0.
I guess I should look at the first of the two :)

STABLE-BRANCH-2-0 344d72b
has the fix. Patch below.

Sounds good. I'll test it as soon as we have a kk package for the next release.

This looks pretty much like T1311.

Should probably beretested with Gnupg 2.1(beta or later)
because agent startup might have changed.

This is not a pinentry problem but one of gpg-agent. What version of gpg-agent
are you using?

Werner, please note: this issue is kkc.

Today I just had the problem again (/dev/pts/9, still same verisons as in T1203 (thomas on Jul 29 2010, 03:35 PM / Roundup))