Thanks for having fixed it for master. It's OK so, because a comment to Issue
1236 shows me a workaround (--allow-freeform-uid) until the next release.

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.

Also fixed in the old dirmngr, svn 347

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 :)

Fixed in dirmngr and also in GnuPG trunk. Patch for gpg4win created.

As I already explained: It works for me using the qt pinentry!

The release pinentry 0.8.0 version (from 2010-03-03) is based on svn222 (see
tags(pinentry-0.8.0).

Use the released 0.8.0 qt pinentry and not some earlier (i.e. -svnXXX versions).

Just to make sure:
I tested with gnupg 2.0.16 + pinentry 0.8.0-svn234.
You say that I should test gnupg 2.0.16 + pinentry 0.8.0-svn237.
Right?
(But in T1237 (wk on Sep 28 2010, 01:05 PM / Roundup) you wrote: "you need a newer gnupg".)

2.0.16 should be sufficient, though. Just use a recent pinentry-qt.

Right, you need a newer gnupg. Pinentry has no i18n support, thus your tests
are pointless.

Just to note:
I tested with the debian package pinentry-qt (0.8.0.svn234-0kk1) from
files.kolab.org. It's the same problem with pinentry-qt and pinentry-gtk (see
test below).
You wrote that pinentry-qt works corectly since 0.8.0 (=svn222). I can't confirm
this with my test below. Or do you mean, that the additional changes in gnupg
are required for show the german "Abbrechen" button text in pinentry-qt?

Hi Werner,

Applied to trunk.

D116: 298_pinentry-qt-fix-1162.diff

Am Dienstag, 8. Juni 2010 12:29:40 schrieb Marc Mutz:

so I've attached the diff to current
pinentry SVN here. Works for me. Kwin/qt3 from etch for Qt3-version,
Qt-4.4.3 (self-compiled) + kwin/qt3 for Qt4-version.

The docs say on some X11 WM's, this flag will have no effect when not also
WX11BypassWM is passed, but the latter robs pinentry of it's title bar and
borders, so I left it out.

Testing pinentry Version: 0.8.0.svn231-0kk1
with window manager kwin from kdebase Version: 4:3.5.9.dfsg.1-6+lenny1.

No info received - assuming everything is fine now.

Changed the test framework again. Now it works on the buildfarm.

Not quite. It does not work on Solaris when build on a NFS mount.

Let me know if I shall do a 0.8.1 release.

Thanks.

The patch seems working

Sorry, I mixed that up with something else. It is indeed a bug in 1.4.10 but
not in the current 2.0 code. I developed a fixed for this which detects a v1
card and forces sha1/rmd160 only in for these cards.

D123: 283_bug1194-fix.diff

There is GpgOL 1.0.1 coming with Gpg4win 2.0.1. Can you give that a try?
Please also state the precise version of Windows and Outlook you are using.

many releases in the meantime thus I am pretty sure that this has been solved -
at least on the GnuPG side.

2.0.1 has been released quite some time ago. Closing.

2.0.14 has been released - closing.

Fixed in all branches. rev. 5236. Patch for 1.4.10 below:

will be in 1.4.5 to be released in a few minutes.

According to the wrieshark tracker, this has been solved.
Fix will be in 1.4.5.

As suggested I have excluded the ID 17 on W2000 systems. I never had this
problem on my W2000 system, so I can't test whether this is sufficient. Please
try the test dll at:

Asg: send me an email saying:

Asg, could you test 2.0.1rc1?

Asg, could you test 2.0.1rc1?

Fixed in 1.4 since 2009-07-23.
Released with 1.4.10.

Hi,
Retested using Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308)
Issue seems to be resolved in that non-encrypted attachments open in a
reasonable timeframe.
Thanks,
Juicefruits.

Duplicate of T1107

Seams to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users.

Fixed again. (svn 5122).