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

Indeed, I applied it only to gnupg-2. Applied it to 1.4 now.

Ooops, I missed to copy the included files. I added a new make traget to assist
me in the future.

2009-04-02 Till Adam <till@kdab.net>

Sorry for the late response, only recently a new pinentry got released.
So we will test this on basis of 0.7.6.

Done. (rev 5092).

Will this be backported to 1.4 as well?

No, --fix-trustdb is a hidden command and may get a new life in the future.

Thanks for the change, I will check it out.
Did you consider removing the option --fix-trustdb
if you do not intend to implement it?
I would consider removal to be good, if the warning
is all what people get in the foreseeable future.
The existance of the options assumes that there is code
to do the fixing behind it.

ping

The translation in zh_TW.po looks good, but the one in zh_CN.po doesn't. It
contains the kanji sequence "删除" (U+5220, U+9664) which is very close to "削
除" (U+524a, U+9664, "remove" in Japanese) in shape.