Somehow I expected such a report (too many open fds). We will need to replace our select based code by poll. However, I think this is more related to T3529.

Thanks for your patches. I decided to do this similar but I need to take several branches in account.

Please do not post warning. They are called warnings for a reason.

Please ignore them.

The new tool is called txxmpp.

Fixed for 2.2. Thanks.

All source code which makes up the installer is distributed by us. Signed by one or more of the core developers.

I disabled your account. If might be possible to remove mail addresses from the DB but I don't known how to do that.

Virus scanner look for patterns seen in known viruses. However, legitimate software may have the same pattern as other software and thus also in viruses.

Nice code. Need to revisit the jabber protocol to understand what to do.

I am now looking into libstrophe.

Well yes. However I had an agreement with Brenno to link to his site. I'll ping him.

In any case those old howtos need some rework.

Sorry, we can't do anything about it. It is a link to an external site.

Unconditionally retrying without SRV lookup is not a good idea. SRV record are there for a reason. What we could do is an option to skip SRV record lookups.

In T3056#95172, @wiz wrote:

Oh, to make it clear - I was testing the pkgsrc version with the additional patches used by pkgsrc, see http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/security/gpgme/patches/

Testing it without patches does not work because:

get-env.c:57:2: error: #error Use of getenv_r not implemented.
 #error Use of getenv_r not implemented.

This is the actual error message from your log file:

2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: idVendor: 04E6  idProduct: 5119  bcdDevice: 0525
[...]
2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver:   bMaxCCIDBusySlots       1
2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: CCID submit transfer (83): 0
2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: CCID: card inactive/removed

To compute the key validity (trust) more information may be needed and we can only do that after the changes have been saved. Further, no-auto-chec-trustdb will anyway delay that computation until "gpg --check-trustdb" is run (e.g. by a cron job).

Frankly, I do not understand your problem. We do _not have_ and useful information in the commit logs before December 1 , 2011. You may find some ChangeLog entries in older commit logs but that is from a time when _I_ used a script to copy the ChangeLog entries into the _CVS_ commit logs. That was never done consistently. Thus by looking at the commit log you will get a wrong picture. This is why we need to keep the ChangeLog-2011 files which start right at the top with

You may have other changes on your system as well.

Should avoid the problem. Then import or create n OpenPGp key first and the next time you should(tm) not be bnotered by the bug.

Okay, I took your suggestion but also improved the documentation. Fixed in 2.2

Oh that is not good. A passed arg should not be closed by the called fucntion unless that fucntion is documented as gaining ownership of it. Let me check.

So you either need to start pcscd or you fix the permission of the device so that GnuPG's scdaemon can access the card reader using its internal access method. There are probably some udev rules which need to be adjusted. For a quick check you can manually change the owner or group to your own user or one of your groups. Then it should work again.

Entering on the shell

lsusb | grep USB

This is verly likely be fixed with commit 5ecef193bc2144e6d51a6bd5727bfd08a0d28b66 which will be released with the next gpg4win version.

Done for libassuan

This has been fixed a while ago my having dirmngr print a hint on the possible problem. gpg will then print a warning about a problem with the Tor configuration and with --verbose print the hint on solving this as well.