Mailing List Archive

Problem regarding dirmngr on Debian stable
Good day.

I saw that the version of GnuPG on Debian stable was not really up
to date and thus decided to build my own local copy from recent sources.

This went really well and I end up with :

$ uname -a
Linux styx 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64
GNU/Linux
$
$ which gpg
/home/dclarke/local/bin/gpg
$
$ gpg --version
gpg (GnuPG) 2.3.8
libgcrypt 1.10.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/dclarke/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
AEAD: EAX, OCB
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
$

I was careful to ensure the linker set RUNPATH to a correct location :

$ readelf -delV $HOME/local/bin/gpg | grep -E 'NEED|NAME|PATH'
[ 8] .gnu.version_r VERNEED 0000000000004548 00004548
0x0000000000000001 (NEEDED) Shared library: [libz.so.1]
0x0000000000000001 (NEEDED) Shared library: [libbz2.so.1.0]
0x0000000000000001 (NEEDED) Shared library: [libgcrypt.so.20]
0x0000000000000001 (NEEDED) Shared library:
[libgpg-error.so.0]
0x0000000000000001 (NEEDED) Shared library: [libassuan.so.0]
0x0000000000000001 (NEEDED) Shared library: [libnpth.so.0]
0x0000000000000001 (NEEDED) Shared library: [libpthread.so.0]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
0x000000000000001d (RUNPATH) Library runpath:
[/home/dclarke/local/lib]
0x000000006ffffffe (VERNEED) 0x4548
0x000000006fffffff (VERNEEDNUM) 6
$
$ ls /home/dclarke/local/lib/libgpg-error.so.0*
/home/dclarke/local/lib/libgpg-error.so.0
/home/dclarke/local/lib/libgpg-error.so.0.33.1
$ readelf -delV $HOME/local/lib/libgpg-error.so.0.33.1 | grep -E
'NEED|NAME|PATH'
[ 7] .gnu.version_r VERNEED 0000000000003068 00003068
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
0x000000000000000e (SONAME) Library soname:
[libgpg-error.so.0]
0x000000000000001d (RUNPATH) Library runpath:
[/home/dclarke/local/lib]
0x000000006ffffffe (VERNEED) 0x3068
0x000000006fffffff (VERNEEDNUM) 1
$

Also I did configure with --enable-all-tests and the test suite ran
perfectly.

However I see messages about some dirmngr issue :

$

$ gpg --keyserver pgp.mit.edu --search-keys blah-blah-blah-keyid
gpg: WARNING: server 'dirmngr' is older than us (2.2.27 < 2.3.8)
gpg: Note: Outdated servers may lack important security fixes.
gpg: Note: Use the command "gpgconf --kill all" to restart them.
gpg: data source ....

There is no dirmngr binary on this machine anywhere.

$ su -
Password:
styx#
styx# cd /usr
styx# find . -type f | grep 'dirmngr' | wc -l
0
styx#

Why am I seeing this strange message ?



--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Problem regarding dirmngr on Debian stable [ In reply to ]
On Samstag, 22. Oktober 2022 19:12:23 CEST Dennis Clarke via Gnupg-users wrote:
> I saw that the version of GnuPG on Debian stable was not really up
> to date and thus decided to build my own local copy from recent sources.
[...]
> $ gpg --keyserver pgp.mit.edu --search-keys blah-blah-blah-keyid
> gpg: WARNING: server 'dirmngr' is older than us (2.2.27 < 2.3.8)
> gpg: Note: Outdated servers may lack important security fixes.
> gpg: Note: Use the command "gpgconf --kill all" to restart them.
> gpg: data source ....
>
> There is no dirmngr binary on this machine anywhere.

/usr/bin/dirmngr is part of the dirmngr package on Debian stable.
https://packages.debian.org/search?searchon=contents&keywords=dirmngr&mode=path&suite=stable&arch=any

> Why am I seeing this strange message ?

Did you check whether there is an old dirmngr still running? Did you run
`gpgconf --kill all` as recommended by the above message?

Regards,
Ingo