Some customers have the problem that the NameUserPrincipal we query over GetUserNameEx does not match the real email address of the user. The display name does not always give the desired result for the name, either.
Optionally, Kleopatra should query AD for the full name (or first name and surname) and the email address. dirmngr can be used to query AD.
Thinking about this, the best way to avoid AD code in Kleopatra would probably be to just create a QProcess that executes Powershell or WMIC to query the AD.
Here are more examples:
https://stackoverflow.com/questions/10184052/get-a-users-email-address-from-the-username-via-powershell-and-wmi
To query the AD I used the GPGME function gpgme_op_assuan_transact_ext with an query string like this:
ad_query --subst --attr=dn,userAccountControl (&(objectcategory=person)(objectclass=user) (|(userPrincipalName={{email}}) (mail={{email}})))Of course {{email}} must be replaced with the mail address queried, this might probably also be the UserPrincipalName.
I finished a first implementation.
Questions:
It turns out that checking for a running dirmngr and then starting it takes a lot of time.
gpgme logs of check for running dirmngr by doing gpgme_op_assuan_transact("GETINFO version", ...):
2026-05-27 09:02:48 gpgme[5376.10d4] assuan_socket_connect (ctx=0x000001b1ccae0e90): call: name=C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.dirmngr, flags=0x0\n 2026-05-27 09:02:48 gpgme[5376.10d4] _assuan_socket (ctx=0x000001b1ccae0e90): enter: namespace=2,style=1,protocol=0\n 2026-05-27 09:02:48 gpgme[5376.10d4] _gpgme_io_socket: enter: domain=0x0000000000000002 type=1, protp=0 2026-05-27 09:02:48 gpgme[5376.10d4] _gpgme_io_socket: leave: hdd=0x000001b1cc862810, fd=0, sock=0x0000000000000c44 2026-05-27 09:02:48 gpgme[5376.10d4] _assuan_socket (ctx=0x000001b1ccae0e90): leave: result=0\n 2026-05-27 09:02:48 gpgme[5376.10d4] _assuan_connect (ctx=0x000001b1ccae0e90): enter: socket=0,addr=0x00000041227fb560,length=16\n 2026-05-27 09:02:48 gpgme[5376.10d4] _gpgme_io_connect: enter: fd=0x0000000000000000 addr=0x00000041227fb560, addrlen=16 2026-05-27 09:02:50 gpgme[5376.10d4] _gpgme_io_connect:2162: error: Input/output error (5)\n 2026-05-27 09:02:50 gpgme[5376.10d4] _assuan_connect (ctx=0x000001b1ccae0e90): error: Input/output error\n 2026-05-27 09:02:50 gpgme[5376.10d4] assuan_socket_connect (ctx=0x000001b1ccae0e90): call: can't connect to `C:\\Users\\g10code\\AppData\\Local\\gnupg\\S.dirmngr': Input/output error\n\n
Corresponding process monitor logs (ignore the different timestamps; no idea why they are different):
9:03:03.0745248 AM kleopatra.exe 5376 CreateFile C:\Users\g10code\AppData\Local\gnupg\S.dirmngr SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:03.0755726 AM kleopatra.exe 5376 QueryEAFile C:\Users\g10code\AppData\Local\gnupg\S.dirmngr SUCCESS c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:03.0897074 AM kleopatra.exe 5376 ReadFile C:\Users\g10code\AppData\Local\gnupg\S.dirmngr SUCCESS Offset: 0, Length: 22, Priority: Normal c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:03.0898639 AM kleopatra.exe 5376 ReadFile C:\Users\g10code\AppData\Local\gnupg\S.dirmngr END OF FILE Offset: 22, Length: 8,192 c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:03.0899011 AM kleopatra.exe 5376 CloseFile C:\Users\g10code\AppData\Local\gnupg\S.dirmngr SUCCESS c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:03.5996913 AM kleopatra.exe 5376 TCP Reconnect g10-win11:57293 -> g10-win11:59188 SUCCESS Length: 0, seqnum: 0, connid: 0 c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:04.1148715 AM kleopatra.exe 5376 TCP Reconnect g10-win11:57293 -> g10-win11:59188 SUCCESS Length: 0, seqnum: 0, connid: 0 c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:04.6246102 AM kleopatra.exe 5376 TCP Reconnect g10-win11:57293 -> g10-win11:59188 SUCCESS Length: 0, seqnum: 0, connid: 0 c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:05.1375932 AM kleopatra.exe 5376 TCP Reconnect g10-win11:57293 -> g10-win11:59188 SUCCESS Length: 0, seqnum: 0, connid: 0 c:\Program Files\Gpg4win\bin\kleopatra.exe 9:03:05.1376972 AM kleopatra.exe 5376 TCP Disconnect g10-win11:57293 -> g10-win11:59188 SUCCESS Length: 0, seqnum: 0, connid: 0 c:\Program Files\Gpg4win\bin\kleopatra.exe
It seems to be the connect system call that's trying to connect for 2 seconds. No idea whether there's something we can do.
Possible solution: Kleopatra starts a dirmngr in the background after the initial keylisting.