Done for 2.0.13:

In GPGME, I made some changes to libassuan to avoid the need for sleeping in all
asynchronous cases (these have yet to be backported into libassuan proper). The
only place where it is left is process_request, which is supposed to be
synchronous. But I wonder if process_request can't do with just setting the
socket to blocking (if it isn't already).

Can someone please check this?

Does the roaming mean that windows constantly syncs the two directories? If
that is the case, the missing locking was indeed a problem. However, depending
on how Windows does it, the new locking code won't help, because gpg does not
take a FileLock on the actual file but on FILE.lock.

File locking is now implemented for W32 (svn rev 4992).

The problem for me is that I'm using a Windows Roaming profile. That means I'm
using a COPY of my profile on 2 separate machines. Any changes on one machine
are not detected by the other. On logout, any changes are synched backl to the
Profile Server.
To get round this, I need to stop using the Windows Profile area to store keys.
I stumbled on this...
http://lists.gnupg.org/pipermail/gnupg-users/2008-April/033224.html
...and set my gpg.conf to the following...

There are two problems: The first is that GPA uses GnuPG-1, I need to check
this but it should not matter because the problem in T1008 is that the
gpgconf tool from GnuPG-2 is missing. There is no problem using both versions
of GnuPG at the same time.

Thanks for the info. This may be related to:
T1008
...where GnuPG2 doesn't get installed sometimes.

You are the first one to report this, despite that GnupG for Windows is 9 years
or so old. It is not only a problem with several PCs but if you run several
several GPG processes on one box. The file locking is simply missing.

Okay, fixed in SVN 4958.

Fixed in SVN revision 4928 in both branches. Thanks.

Okay, I can duplicate on a powerpc64.

Just as a quick follow-up to this script I wrote:

awaiting backport to 1.4.

Fixed in dirmngr svn revision 300.

Thanks!

D56: 167_gpgsm-ext-keylist.diff

Not quite correct. The error was probably handled. The actual cause is that we
introduced a new error message in dirmngr. Find attached a patch against the
current gnupg to fix it. Should apply to 2.0.9 as well.

Fixed in SVN 4714 to be released with into 1.4.9 and 2.0.9. This was actually a
possible memory corruption around deduplication of user IDs.

Found it. The code to bypass the MIME parser missed to cleared info fields used
to colelct the mime structure. Fixed in svn 235.

The SVN number seems to be from the gpg4win installer. The current GpgOL
revision is 233.

Outlook crashed after import .pst file and double click on the encrypted or
signed+encrypted email.
Signed messages (with/without attachment) don't show cleaned mail body content.
Still the same problem... Tested with svn739.

Decryption works now.

Additional problem is that the test messages don't contain a final LF. This is
a usual problem with PGP armored messages. I have added a hack to overcome this
problem.

Now fixed in SVN 222.

Well, not really. IT requires a more complicated solution.

-----BEGIN PGP SIGNED MESSAGE-----

Fixed. Will be released with 1.4.8rc1.

Works for me. However I was not able to replicate the original case because I
have no 2.0.5 available.

Fixed in SVN. I can't see a regression here, through.
Here is the short fix:

We need to fix the symptom as there is always the possibilitiy of
duplicates and that should not inhibit the use of gpgsm.

2.0.6 ahs been released, so closing.

Taking bug.

Todd Zullinger told me that it needs to UTF-8 encoded.

A new webpage has been written and is available on www.gnu.org. However the
index file is not yet shown. This is probably a problem with the symlink
creation. Need to call the webmasters.

Applied for a new Savannah project

Fixed in SVN.

Unfortunately, the command-line version does the exact same thing. :(