Do not use this legacy debug stuff. Use --debug CATEGORY. For example

It is not just about being annoying but for security reasons. It would be too easy for other applications *think webbrowser or Acrobat) to take a screenshot and pop up a modified version of that screenshot with data entries to act as a MitM.

Can you check which dirmngr version you are running

gpg-connect-agent --dirmngr 'getinfo version' /bye

It does not work either. Your problem is the use of a wildcard DNS for archlinux32.org:

The test above was with gpg master but I got the same result with current 2.2:

Thanks. Here is a dirmngr log:

Does your ngix configuration mean that there is no fallback to standard http?

The message has not been encrypted to you. Ask the sender to encrypt to you.

There is no need to use the new CTB format for a packet with tag 3. OpenPGP implementations need to support all packet header encodings. We do not plan to make this configurable.

Agreed.

Given that 1.5 already had that problem, I would suggest to ignore that bug for the 1.6 release. We can work on that later.

You mean the default key is expired?

This seems to be closely related to T4319 and due to to some, ahem, interesting configuration.

BTW: I have the problem that I want to know the keys of all cards. "getinfo card_list" along with --demand can be used for this. gpg-card works this way. It does not work if plug in addtional cards becuase card_list shows only the cards for which a SERIALNO command has been used. A new feature to scan the buses for all readers and cards would be quite useful.

Thanks for the detailed implemention plan. For the include-historic et al things it might be better to make use of the filter-syntax. I am not sure what is bets but that get clearer during coding. First step will be to add a parser and to silence 2.2 about this. I can imagine to later backport some basic functionality to 2.2

Thanks for the sample certs. I noticed the posts but had not the time to look into them.

Sorry, we don't use or support PIP. Please ask whoever packaged that for PIP.

The Python doc build system we implemented the last year is a complete mess - I had so much trouble the last time I did a release :-(.

Thanks. Fixed in stanble and master.

Please read my answer again. Posting to gnupg-users does not require a subscription.

See T4683 and T4684.

oops: That was an accidential priority change

The mentioned "strange hangs" would only be solvedwhen using master - in 2.2 we already had proper locking.

Implemented master and 2.2. Note that the comment in the master commit about possible reason for stucked keylisting in gpgsm is only related to master.

I implemented it nearly as suggested. However, the default AKL is used, which is "local,wkd" (local is not used with that command though).

Fixed for 2.2.18. To allow seeing these warnings this change will only have an effect if a listing of all keys is requested.